Build on the platform
Your developers build the product. The operated platform includes a storefront template for branded signup, a customer portal, an operator console, sign-in, access controls, notifications and deployment management.
Pricing
A deployment scoped to your SaaS.
Your quote covers the shared platform we operate for your product. Bring your expected customers, environments and support needs. If you want us to build the app or connect existing software, we scope that work with you.
Connect an existing app
Bring the services that already work. We identify the changes your app needs and which optional modules to include, such as support and ticketing, audit, status or AI. Connections to your existing providers are scoped separately.
Commission the application
If you need a team to build it, bring the first task your customer needs to complete. We scope the software, integrations and handover alongside the ongoing platform operation.
What your quote includes
The quote documents the deployment topology, included services, AWS resource allocations, support boundary and price, so the commercial scope matches the operating scope.
Every deployment includes your own managed platform stack on AWS, the platform services, the Control Plane, the App SDK and the support boundary written into the quote. Price is scoped per deployment. Talk to us to scope yours.
Platform scope
The capabilities, tenancy model, environments and customer-facing surfaces included in the deployment.
Tenants & scale
How many tenants you run, expected throughput, background-processing volume, and the minimum and maximum service capacity assigned to their plans.
Cloud footprint
The environments your deployment needs, such as production, staging and recovery, and the isolation boundaries and dedicated components your buyers require.
Plan features & infrastructure
The feature entitlements, quotas and pooled or dedicated AWS resources attached to standard and customer-specific plans.
Implementation path
The first use case, App SDK integration, migration boundaries and the work owned by each team.
Operating model
Monitoring, upgrades, support coverage, response expectations, recovery targets and incident-response cover. Controls are mapped to SOC 2 and ISO 27001, with GDPR controls built in.
Get a deployment-scoped quote
Start with your tenants, environments and timeline. The assessment turns those inputs into a clear scope and commercial proposal.
What your customers pay you
Package features, quotas and infrastructure into plans
Your platform quote covers your deployment. You set the plans and prices your customers pay for your product. Your app declares which features and limits those plans control.
01
Declare the feature
A feature definition in the app contract includes a type, default and quota policy. For example, max_projects is an integer that defaults to 5 and sso is a boolean.
02
Compose the plans
Operators bind values in the Control Plane with no app deploy: Starter caps projects at 5, Pro removes that cap and enables SSO.
03
Publish the plan and enforce it
Customers choose a plan in the portal and your payment provider bills them. Your app applies the subscription, feature and quota checks to the actions that need them. You can change supported plan values without deploying new product code.
Custom plans are configured in the Control Plane.
Operators can create a plan for one organization, set feature and quota values, attach pooled or dedicated AWS resources, and assign the plan without changing product code. A plan can also offer an upgrade from shared components to a dedicated database, dedicated compute, dedicated observability or an isolated stack. Eligible component moves run as tracked provisioning and migration workflows, with alert routing scoped to the resulting deployment. Customers can also add a dedicated database or dedicated compute to their plan themselves from the portal, choosing a size and seeing its price first. The quote records those plan inputs and the assumptions that would change the price.
Sell dedicated infrastructure to your customers
Each app a customer runs can get its own database server, compute, cache and message cluster, for scale or to meet a customer’s isolation requirements. You price and sell them like any other plan feature, and the subscription decides what each customer runs. Combined with a plan made for one organization, this is how you put together a custom enterprise package for a large customer.
- 01
Give each app its own resources
Each app a customer runs can get its own database server, compute, Redis cache and Kafka cluster, at the size you choose. Put them in a plan, or let a customer buy them as a monthly add-on on the subscription they already have.
- 02
Paid first, then provisioned
Nothing is provisioned until the payment is confirmed. Then the platform creates the resource and moves that customer’s workspace onto it, with no ticket and no console step.
- 03
Upgrade, resize or downgrade with the plan
When the subscription changes, the platform compares what the customer is entitled to with what they run, and makes the move: from shared to dedicated, to a larger size, or back to shared. Dedicated compute also scales out on its own, up to the maximum you set, as that app’s load grows.
- 04
Cancel or expire without leftovers
A cancelled add-on keeps its resource until the paid period ends. Then the workspace moves back to shared and the dedicated resource is removed. If a move fails, the add-on is withdrawn and the unused time is credited.
Service targets
The targets we work to
A target we aim for across the service, not a contractual commitment.
Support for your deployment
The support boundary and response expectations for a platform deployment are written into the quote. The response and resolution targets for the SynaptaGrid products are published by plan on the product pricing page.
Common questions
Questions about deployment and commercial terms
Can we charge our customers for dedicated infrastructure?
Yes, app by app. Each app your customer runs can have its own database server, compute, Redis cache and Kafka cluster, included in a plan you sell or bought as a monthly add-on at the price you set. The platform provisions it after the payment is confirmed, moves that customer onto it, follows upgrades and downgrades, and removes it when the add-on is cancelled at the end of the paid period.
Where does the platform run?
On AWS. Your SynaptaGrid deployment runs in its own managed platform stack. Inside it, your tenants can use pooled infrastructure or dedicated databases and stacks according to their isolation tier. Customer data can be placed in the region your customers need, including the EU. Bring-your-own-AWS-account and on-premises deployments are on the roadmap — talk to us about timelines.
Can I bring my own identity provider?
The platform federates with your identity provider through OIDC or SAML, including managed enterprise SSO.
Who owns the data?
You do. Your platform deployment encrypts data at rest and in transit, with dedicated tenant boundaries available by tier. Dedicated deployments can bring their own encryption keys: your database storage, its credentials and your object storage held under a key in your own cloud account, revocable by you.
What if we want to leave?
Tenant data can be exported in documented formats from standard databases. Identity uses OIDC, OAuth, SAML, LDAP and SCIM. The contract can include a defined transition period, migration assistance and continuity terms.