# Service Consumption Tables V.1.0.3 Effective November 4, 2024 #### Overview These Service Consumption Terms are effective as of November 4, 2024 (the "Effective Date") and apply to all customers on Stacksync’s consumption-based pricing model. Stacksync provides automated cloud data pipelines (“Connectors”, “Apps”) to its customers (each a “Customer”, “you”, “your”) as a service that transports data from various sources to specific destinations (the “Stacksync Service”). The service supports unidirectional and bidirectional data sync and is available in multiple plans (“Plans”) hosted across various geographical regions ("Regions") by third-party cloud providers (“Cloud Providers”), as described in your agreement with Stacksync (“Agreement”). Event-based actions (“Triggers”) may be initiated based on data activity within Connectors. #### Definitions * **Workspace:** The customer’s collaborative space attached to a subscription. Each workspace has exactly one active subscription. A Workspace contains Connectors and Destinations grouped into Syncs. * **Sync:** Two or more apps connected together with data in sync. A Sync may be active, paused or deleted. Syncs are organized within workspaces. * **Account:** The Customer’s account on Stacksync. An Account may own or have access to multiple workspaces. An Account contains personal data about the customer. * **Arrears:** For Capacity Purchases (defined below) only, this means any additional usage after the initial purchase has been used, but before the end of the original term. The Arrears period ensures you are able to continue using the Stacksync Services, even if the original Contracted Spend has already been consumed. You will be alerted by Stacksync when you are in Arrears. * **Subscription:** A paid plan attached to a workspace. * **Billing Period:** A calendar month running from the first to the last day of the month. * **Capacity Purchase:** A subscription-based plan which requires an annual upfront purchase of Contracted Spend in bulk. * **Contracted Spend:** The total dollar amount purchased as listed in the Order Form. Contracted Spend is shown on an annual basis. * **Destination:** A destination is a data warehouse, database, data lake, or data lake house where the data is delivered. * **Incremental Spend:** The price charged for the next thousand **Records in sync** (or portion of the next thousand **Records in sync**) consumed after surpassing the **Records in sync** Threshold for the month in question. * **Initial Sync:** The first time that a connector completes a historical sync. * **Monthly Purchase:** A plan which is not subscription-based, whereby a Customer is billed monthly in-arrears for their usage during the prior Billing Period. Monthly plans are available to purchase at the (i) stacksync.com user interface or through the (ii) AWS, (iii) GCP, or (iv) Azure marketplaces. * **Records in sync:** The number of distinct Primary Keys synced via Stacksync, calculated on a per-Sync basis. We only count a row once per Billing Period, even if it syncs multiple times. * **Records in sync Threshold:** The minimum **Records in sync** usage requirement to receive the consumption rates on the Service Consumption Table below. * **Monthly Spend:** The dollar amount consumed each Billing Period from your Contracted Spend based on your actual monthly usage. * **Total Monthly Spend:** Total Monthly Spend is the sum of Monthly Spend on Connectors and any other applicable uses of the Stacksync platform and Services. * **Order Form:** The form used to purchase Contracted Spend from Stacksync. For Capacity Purchase customers, this is an order form document. For Monthly customers, this may be an order form document or may be the terms attached to a Monthly Purchase through one of the marketplaces identified above. * **Plan:** The bundle of features included as a part of your Stacksync Service and outlined here. Plans may be Capacity Purchase plans (subscription-based) or may be Monthly Purchase plans (do not require annual subscriptions). * **Primary Key:** A unique identifier that specifies a distinct row within a table. In bidirectional sync mode, the primary keys of the rows in the synced apps are mapped together. In this context, the Primary Key corresponds to a unique mapping. For instance, a corresponding row in synced apps within the same Sync results in only one Primary Key. ### Records in sync **Records in sync** represents the number of distinct Primary Keys processed per Workspace per Billing Period. If a Primary Key is synced multiple times, it counts as one **Record in sync**. Up to 50% of the **Records in sync** for an Initial Sync is excluded for each new Sync. In cases where network troubleshooting is needed, Customer cooperation may be required to allow data flow to Stacksync. **Records in sync computation** Records in sync serve as billing units and are determined within a billing period of one month. Records in sync billing is based on these actions: 1. **Record changes**: each created, updated, or deleted record within a Billing Period counts as one **Record in sync**. If it is updated multiple times in the same Billing Period, it still counts once. 2. **Triggers:** each successful trigger counts as an additional **Record in sync**. For instance, if a record is updated five times during the Billing Period, and two of those updates activate triggers, only one **Record in sync** will be counted for the five record updates, and two **Records in sync** will be counted for the triggered actions. Thus, a total of three **Records in sync** will be billed for that scenario. 3. **Full crawling requirements:** some systems, like HubSpot, require full crawling to detect changes. All records synced will count as **Records in sync**. All synced records will be counted at least once within a Billing Period if they exist. However, even if full crawling occurs multiple times in the same Billing Period, the records will only count once. If these same records are updated during the Billing Period, they will not count twice because they were already counted once. 4. **Workflow execution**: each successful workflow execution counts as an additional **Record in sync**. Unlike record updates, which are counted once per unique record in a Billing Period, each individual workflow execution is a distinct, billable event. For example, if updating 50 unique records causes a workflow to execute 50 times, this will be counted as 50 Records in sync for the record updates plus 50 additional Records in sync for the workflow executions, resulting in a total of 100 Records in sync. * **API proxy** * **Standard calls**: included up to the plan’s quota, with excess usage billed at the Records in sync rate. * **AI Insights calls**: AI-driven calls (marked with “ai” in the URL) are included up to the plan’s quota and billed at 15 Records in sync per call once the quota is exceeded. #### Service consumption and spend calculation Monthly Spend depends on **Records in sync** usage and the selected Plan. Each Plan has a base price covering limited usage, with incremental costs for usage beyond the included limit. **Plan pricing** * **Starter Plan:** $1400/mo (or $1000/mo billed yearly) * **Pro Plan:** $3700/mo (or $3000/mo billed yearly) * **Enterprise Plan:** custom pricing based on specific requirements **Service consumption table** Additional **Records in sync** pricing (Consumption based). The pricing increments in thousands of **Records in sync**. Each thousand **Records in sync** started, even partly consumed, is due in full. | Records in sync Tier | Price per 1,000 | | -------------------- | --------------- | | 0 - 50k | $0 | | 50k → 150k | $8.00 | | 150k - 1M | $2.00 | | 1M → 10M | $0.90 | | 10M → 100M | $0.40 | | over 100M | $0.10 | **Example of cost calculation** Suppose you’re on a **yearly** Starter Plan with a base price and have used 200,000 **Records in sync** in one month. Here’s how costs are calculated: * First 50,000 **Records in sync**, included in your plan. * Next 100,000 **Records in sync**, priced at $8 per 1,000: 100 \* $8 = $800. * Additional 50,000 **Records in sync**, priced at $2 per 1,000: 50 \* $2 = $100. * **Total Records in sync cost:** $0 + $800 + $100 = $900. * **Total Monthly Spend:** Base Price ($1000) + **Records in sync** Cost ($900) = $1900. #### Custom development services For services outside of standard support, such as custom development, the following hourly rates apply: * **Junior Engineers / Junior Solutions Architects**: $250 USD per hour * **Senior Engineers / Senior Solutions Architects**: $400 USD per hour **Capacity purchase plan** For customers with a Capacity Purchase Plan, usage rates are based on the Service Consumption Table. Multiple Workspaces under one Capacity Purchase Plan can share Contracted Spend but cannot combine Synced Rows for volume discounts. #### What happens when Contracted Spend is depleted? Capacity Purchase Customers will enter an Arrears period if Contracted Spend is depleted, during which they can continue using Stacksync Services at the "Monthly Pay As You Go" rates. Stacksync will prompt customers to purchase additional usage. #### Expiration of Contracted Spend Contracted Spend must be used within the subscription term, with no rollover to the next term. Contact your account representative for renewals or new orders. #### Multiple Workspaces Each Workspace’s Records in sync usage is calculated independently. Combining Rows Synced across Workspaces for discounts is not allowed, but consolidation into a single Workspace is available upon request. #### Support Plans **Support Priorities** Stacksync provides highly responsive support channels. The following priority levels define how issues are classified and handled: **P-0 — Critical / Production Down** * Full production outage or data corruption * Core functionality unavailable * Immediate business impact * Requires instant escalation to on-call engineering **P-1 — High / Severe Degradation** * Major functionality impaired, though partially operational * Significant performance degradation * No viable workaround * Requires rapid attention **P-2 — Medium / Functional Issue** * Non-critical feature malfunction * Business impact present but mitigations available * Addressed during business hours **P-3 — Low / Minor Bug or Usability Issue** * Cosmetic issues or low-impact defects * No operational disruption * Resolved in standard maintenance cycles **P-4 — Inquiry / Feature Request** * Clarifications, documentation questions, or enhancement requests * No operational impact *** **Support Channels** * **P-4 to P-0** issues should be raised via the standard support channels included in your plan (Email, Slack, or Phone). * **P-0** incidents may be escalated through the dedicated 24/7 hotline available under **Workspace Settings → Support Methods** (if included in your plan). Triggering a P-0 escalation immediately notifies an on-call engineer. Your team must be ready to respond in real time (chat and/or call) to ensure rapid resolution. **Note:** Submitting non-urgent or lower-severity issues through the P-0 hotline may incur fees of up to **$1,000 per false alert due immediately**. #### Changes to the Stacksync Service Consumption Table Stacksync may periodically update this Service Consumption Table. When updates are made, the **“effective date”** at the top of the document will be revised. * For **Capacity Purchase plans**, the updated table will apply upon renewal or when entering a new Order Form after the changes go into effect. This holds true if no other agreement between the parties supersedes this Service Consumption Table. * For **Monthly Purchases/Plans**, the updates will apply in the first Billing Period following the new effective date. If a material change is made, Stacksync will make reasonable efforts to notify you through the Stacksync dashboard or via email prior to the update taking effect. #### Benefits per plan Each Plan offers specific benefits as detailed below. Not all features are available in every contract. For Enterprise Plans, benefits are customized and not universally included. Refer to your Order Form for specific entitlements. | Feature | Starter | Pro | Enterprise | | -------------------------------------------- | --------------------- | --------------------- | ---------------------------------- | | **Two-way sync** | | | | | Number of Syncs | 1 | 3 | Unlimited | | Synced records | 50K | 1M | Custom | | Real-time data sync | ✓ | ✓ | ✓ | | One-way syncs | ✓ | ✓ | ✓ | | Two-way syncs | ✓ | ✓ | ✓ | | Automatic data backfill | ✓ | ✓ | ✓ | | Edit sync configuration | ✓ | ✓ | ✓ | | Sync event triggers | ✓ | ✓ | ✓ | | Issues dashboard | ✓ | ✓ | ✓ | | Sync statistics and metrics | ✓ | ✓ | ✓ | | Smart API rate limits | ✓ | ✓ | ✓ | | Basic connectors | ✓ | ✓ | ✓ | | Enterprise connectors | - | - | ✓ | | Early access to preview integrations | - | ✓ | ✓ | | **Workflow automation** | | | | | Number of workflows | 5 | 25 | Unlimited | | Workflow executions | 10K | 1M | Custom | | Configure workflow with YAML/JSON files | ✓ | ✓ | ✓ | | Asynchronous workflow executions | ✓ | ✓ | ✓ | | Synchronous workflow executions | ✓ | ✓ | ✓ | | Replay failed workflows | ✓ | ✓ | ✓ | | Workflow versioning | ✓ | ✓ | ✓ | | Log explorer | ✓ | ✓ | ✓ | | Store logs in your own storage | - | - | ✓ | | Managed ultra-scalable message queues | 1k events /min /queue | 5k events /min /queue | 10M events /min /queue | | Number of managed queues | 1 | 5 | Unlimited | | Variables and Secrets | ✓ | ✓ | ✓ | | Basic connectors | ✓ | ✓ | ✓ | | Enterprise connectors | - | - | ✓ | | **API management suite** | | | | | API proxy | ✓ | ✓ | ✓ | | API proxy access | ✓ | ✓ | ✓ | | API proxy - rate limit | 50k calls/day | 150k calls/day | Unlimited | | **Platform** | | | | | Collaborators per workspace | 3 | Unlimited | Unlimited | | Select processing region | Basic | Extended | All (including custom regions) | | Select cloud provider (GCP, AWS, or Azure) | - | - | ✓ | | Monitoring dashboard | - | ✓ | ✓ | | Log retention policy | 1 day | 7 days | 30 days | | SLAs | - | - | ✓ | | Notification and alerting | Email | Email | Email, Slack, WhatsApp, PagerDuty | | Environments (e.g. Dev, Staging, Production) | 1 | 1 | 3 | | "No data retention" policy | ✓ | ✓ | ✓ | | On-premise deployment | - | - | ✓ | | GovCloud solutions | - | - | ✓ | | White label platform | - | - | ✓ | | **Security** | | | | | Passwordless and social logins | ✓ | ✓ | ✓ | | MFA | - | ✓ | ✓ | | SSO & SCIM | - | - | ✓ | | RBAC (Role Based Access Control) | ✓ | ✓ | ✓ | | SSH tunneling | ✓ | ✓ | ✓ | | Reverse SSH tunnels (annual contract only) | - | - | ✓ | | IP whitelisting | - | ✓ | ✓ | | SSL certificates | - | ✓ | ✓ | | VPC peering | - | - | ✓ | | VPN gateway | - | - | ✓ | | AWS Transit gateway | - | - | ✓ | | GCP CloudSQL proxy | - | - | ✓ | | Private networking for AWS/Azure/Google | - | - | ✓ | | **Compliance** | | | | | SOC2 type 2 | ✓ | ✓ | ✓ | | GDPR | ✓ | ✓ | ✓ | | CCPA | ✓ | ✓ | ✓ | | ISO27001 | - | ✓ | ✓ | | HIPAA | - | ✓ | ✓ | | **Extensibility** | | | | | Stacksync's Management API | - | ✓ | ✓ | | Configuration as code (for Syncs) | - | ✓ | ✓ | | Configuration as code (for Workflows) | - | ✓ | ✓ | | **Support** | | | | | Documentation | ✓ | ✓ | ✓ | | Slack community | ✓ | ✓ | ✓ | | Dedicated Slack support channel | - | ✓ | ✓ | | Email, Chat and phone. Up to 24/7 support. | - | - | ✓ | | Solutions Architect | On Demand | On Demand | Dedicated during setup and monthly | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.stacksync.com/legal/service-consumption-tables.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.