Skip to main content
SynaptaGrid Platform
For B2B SaaS teams selling to enterprises

Build your product. Leave the platform to us.

Your product is the application your customers pay for. SynaptaGrid Platform is the foundation you build, launch, sell and run it on. When an enterprise customer asks for single sign-on, provisioning, an audit trail or EU data placement, your engineers start from finished work instead of building and connecting it themselves, so your next release ships sooner.

Book a demoSee it in 2 minutes

Get a deployment assessment →Building something new, or no engineers? Find your path →

  • Reach your next release with less to build. Enterprise sign-in, provisioning, plans, billing and access already work together.

  • Keep shipping after launch. Build each feature with development tools and ready-made components for settings, permissions and notifications.

  • We run the platform for you. Servers, databases, backups, upgrades and security patches are our job, not your engineers’.

  • Open to your customers’ systems. They reach your app through APIs, webhooks and their own AI assistant. See how customers use your app through APIs and AI agents →

Build & integrate
Customer experience
Sell
Bill
Run your business
Building blocks
Trust & compliance
Infrastructure
Headless APIs
App SDK
App declaration
SDK command line
UI kit & tables
MCP for AI assistants
Developer docs
Time zones
Localization
Customer portal
Enterprise sign-in
Notifications
Support & live chat
Knowledge base
Status & uptime
App marketplace
White-label branding
Custom domains
Storefront & sign-up
Pricing page
Plans
Features & quotas
Free trials
Discount codes
Add-ons
Checkout
Subscriptions
Invoices
Custom invoices
Custom extensions
Usage & credits
Tax IDs & VAT
Failed-payment recovery
Refunds
Operator console
Organizations
Members & invites
Service accounts
Roles & permissions
Settings
Audit trail
Onboarding
Analytics
Cloud cost visibility
Comments & mentions
Import & export
AI & MCP
Events & webhooks
Background jobs
Safe retries
Undo & restore
File storage
Rate limits & quotas
SOC 2 & ISO 27001 audit-ready
Security controls
Privacy & GDPR
Data separation
Bot protection
Login lockout
Password strength checks
Data residency
Customer-managed keys
Dedicated resources
Databases
Backup & recovery
Pipelines & releases
Domains & DNS
Web firewall
Key & secret rotation
Enterprise observability
Multi-region
Users table
Login form
Our first enterprise customer wants SAML.
SCIM provisioning?
How do we invite a whole team?
Who is allowed to see what?
How do we take card payments?
Tax IDs and VAT on invoices?
What happens when a payment fails?
How do we bill a custom contract?
Where do support tickets go?
Response targets for the enterprise plan?
Is our service up right now?
Brute-force login attempts?
Can support help a customer safely?
Where does European data live?
What about GDPR?
A dedicated database for one big customer?
Backups we can actually restore?
How do we prove it to an auditor?
Where do I store my users?
How do they sign in?
LDAP? Active Directory?
MFA for every account?
MCP, so their AI tools can reach us?
Free trials?
Discount codes?
Refunds?
How do customers see their own tickets?
Will our emails reach the inbox?
Bots hammering the sign-up form?
Weak or leaked passwords?
Rotating API keys?
Retries without double-charging?
How do we undo a bad change?
Their own branding and domain?
Other languages and time zones?
Your appYour product, your logic
The integration

12+ months of work in a few calls, done properly

projects.py
@router.post(    "/v1/my-saas/portal/projects",    dependencies=[        Depends(RequireAuthz("project", "create")),        Depends(require_active_subscription),        Depends(require_feature("projects")),        Depends(require_quota("max_projects", current_usage=count)),    ],)async def create_project(payload: ProjectCreate):    # Every check passed. Your code does the work.    return await save_project(payload)
PermissionMay this person create a project?
SubscriptionIs the customer’s subscription active?
Plan featureDoes their plan include projects?
QuotaAre they within the plan’s limit?
App SDKsPythonTypeScriptAPI clientsGoRustPHPChecked on every call, before your code runs
The standard

Secure, scalable and operable by design

Security

SAML, LDAP, SCIM and MFA
Short-lived, rotating tokens
Encryption in transit and at rest
Least-privilege roles
Separate customer data

Scalability

AWS auto scaling on CPU and memory, per service
Floors, ceilings and schedules you set
Fargate, EC2 or Spot capacity, larger tasks when needed
Dedicated workers and databases for heavy customers
Read replicas, multi-zone and multi-region

Operability

Health checks on each service
Enterprise observability and alerting
Reviewed, numbered releases
Live uptime checks and incidents
Tamper-evident audit trail

Compliance

Audit-ready for SOC 2 and ISO 27001
Aligned with ISO 27017, 27018 and 27701
GDPR export and erasure
Regional placement in the US or EU
Terms and Privacy per region
Every company starts with an idea. Your app.
Your core business: the logic only your team can build.

Where to start

  • Audit-ready for SOC 2 and ISO 27001
  • Encryption at rest and in transit
  • US or EU placement available
  • Tamper-evident audit trail
  • Trust Center →
The problem

Your first enterprise customer sends a list. How much of it is built?

Your product already does what it should. Before a larger company signs, its IT, security and finance teams ask questions like these, and each one lands on your engineers. The same list is waiting whether you are launching or already selling. SynaptaGrid Platform has already answered them.

Sign-in and access

Plans and billing

Support

Security and privacy

  • Brute-force login attempts?

    Answered by Login lockout

  • Can support help a customer safely?

    Answered by Support access

  • Where does European data live?

    Answered by Data residency

  • What about GDPR?

    Answered by Privacy & GDPR

Operations

Already have sign-in and billing? Keep what works, and compare what your team would still build, connect and maintain.

Compare what your team builds and operates →No engineering team? We can build it for you →See every capability →
How it works

One customer, from sign-up to support

Follow one company from its first sign-in to its first support request. Each step starts from the one before: the payment sets the plan, the plan sets what the team can use, and you see every customer from one console. Nobody on your team connects these steps by hand.

  1. 01Your customer

    A customer signs up with their company login

    They register on your branded page, or sign in through their company’s identity provider.

    Handled by

    • Enterprise sign-in
    • Notifications
  2. 02Your customer

    They pick a plan

    Your pricing page lists the plans and the features you set for each one.

    Handled by

    • Pricing page
    • Plans
    • Features
  3. 03Your customer

    They pay at checkout

    A card payment starts the subscription and the plan takes effect.

    Handled by

    • Checkout
    • Subscriptions
  4. 04Your customer

    They invite their team

    Colleagues get an invitation and the role you defined for them.

    Handled by

    • Members & invites
    • Roles & permissions
  5. 05In your app

    Everyone works in your app

    Your app opens for that company, with its data kept apart from every other customer’s.

    Handled by

    • Your app
    • Data separation
    • Databases
  6. 06Your customer

    They get invoiced every month

    Invoices are generated and sent, and usage is counted against the plan.

    Handled by

    • Invoices
    • Usage & credits
    • Notifications
  7. 07Your customer

    They ask for help

    Tickets and live chat reach your support team from the customer portal.

    Handled by

    • Support & live chat
    • Knowledge base
    • Customer portal
  8. 08You

    You run it all from one console

    You see every customer, adjust a subscription and check who changed what.

    Handled by

    • Operator console
    • Custom invoices
    • Custom extensions
    • Audit trail
Inside the product

See the platform your team will operate

The Control Plane your team uses, and the self-serve portal your customers use.

cp.synaptagrid.io/analytics
Platform analytics: active and trialing tenants, subscription mix, churn rate and net subscription movement
Every subscription change feeds tenant health, revenue, churn and conversion figures.

Customer surface

A branded self-serve portal is included

Subscriptions, invoices, applications, team and service accounts, all connected to the same platform.

acme.synaptagrid.io/portal
Customer portal dashboard: the workspace apps, plan and usage, team and support at a glance
Customers see their apps, plan usage, team and open support tickets on one page.
Dedicated infrastructure

Sell dedicated infrastructure as part of your plans

Your largest customers want their own infrastructure, to handle their scale or because their security and compliance rules require isolation from other customers. With SynaptaGrid Platform you sell it in a plan or as an add-on, app by app, and the platform provisions, moves and removes it as the subscription changes. That is what lets you offer a custom enterprise package: their own plan, their own isolated infrastructure, their own price.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

How shared and dedicated resources work →
Your part

Your team builds the product, with our toolkit

Your developers write the rules and screens that make your product different. The next feature reuses the same permission check, settings editor, tables and notifications instead of building them again.

Declare your app once

Roles, plans, settings and events go in one declaration file. Validate and publish it from the command line.

Check access in one call

App SDKs for Python and TypeScript give every request its customer context and check the user’s permission, the subscription and the plan feature together.

Reuse the screens every feature needs

Data tables with search, filters and export, field editors, and generated settings screens that handle drafts and saves.

Keep your own front end

Your screens call platform APIs for access, settings and shared services. The docs cover the APIs, keys and rate limits.

Start from more than an SDK

A service template

Start a new backend service from a template that already boots, migrates and passes CI, with a worked example of each platform pattern to replace with your own domain.

Embeddable UI packages

Drop in ready React packages for sign-up, billing and credit purchases, an AI assistant chat panel and import and export, instead of building those screens.

Your marketing website

Your public site can list your plans and prices from the platform and register new customers with the sign-up package, so the website and the product sell the same plans.

See the App SDK →

One endpoint, four checks: the permission, an active subscription, the plan feature and the quota.

@router.post(
    "/v1/my-saas/portal/projects",
    dependencies=[
        Depends(RequireAuthz("project", "create")),  # permission
        Depends(require_active_subscription),        # subscription
        Depends(require_feature("projects")),        # plan feature
        Depends(require_quota("max_projects", current_usage=project_count)),  # quota
    ],
)
async def create_project(payload: ProjectCreate):
    return await save_project(payload)
See the full example in Python, TypeScript, Go, Rust and PHP →
Inside the pieces

Each piece is a complete system

When a security review or an IT team goes deeper than the list, open the part it asks about. Each one is a working system with its own settings, permissions and records, from storing a customer’s files to connecting an AI assistant.

Decide who can do what, down to a single record.

Roles, attribute policies and relationship rules in one engine, checked on each request.

  • Roles & permissions

    Your roles ship with your app.

  • Custom roles

    Customers define their own.

  • Attribute policies

    Decide by department, region or any attribute.

  • Relationship rules

    Access through ownership and hierarchy.

  • User groups

    Give a whole team a role at once.

  • Time-boxed access

    Grants that expire on their own.

  • Support access

    Help a customer without sharing passwords.

  • Changes on record

    Role and permission changes are audited.

APIs, AI agents and webhooks

Make your SaaS accessible to customer systems and AI agents

Let your customers choose where they work. Their people use your screens, their systems call your API, and an AI assistant can use the same actions: through MCP from the assistant they already use, or in the chat built into your product.

Declare an action once, and it works in your screens, your API and AI assistants over the Model Context Protocol (MCP), with the same permission checks everywhere.

Let a customer’s own systems use your app

The customer’s system calls your API with a workspace service account: its own key and role, revocable without touching anyone’s login.

Service accounts and API access →

Let a customer ask an AI assistant

A user asks their own AI assistant. Every lookup runs with the signed-in user’s permissions, and the customer admin chooses which tools are on.

AI tools and MCP →

Notify a customer’s system when something changes

A customer subscribes its system to supported events in the catalogue and receives signed webhooks it can verify.

Events and signed webhooks →
The standard

Secure, scalable and operable by design

The platform is audit-ready for SOC 2 and ISO 27001 and aligned with ISO 27017, 27018 and 27701, with the controls, evidence and audit trail an auditor asks for.

  • SOC 2Audit-ready
  • ISO 27001Audit-ready
  • ISO 27017Aligned
  • ISO 27018Aligned
  • ISO 27701Aligned
  • GDPRBuilt in
  • US regionIn productionThe platform runs in the United States today.
  • EU regionPlacement availableA customer whose data must stay in Europe can be placed in the EU region.
  • Terms and PrivacyPer regionWrite your Terms, Privacy and Refund policies once, override them where a region needs its own, and keep a record of the version each user accepted.

Security

  • SAML, LDAP, SCIM and MFA
  • Short-lived, rotating tokens
  • Encryption in transit and at rest
  • Least-privilege roles
  • Separate customer data

Scalability

  • AWS auto scaling on CPU and memory, per service
  • Floors, ceilings and schedules you set
  • Fargate, EC2 or Spot capacity, larger tasks when needed
  • Dedicated workers and databases for heavy customers
  • Read replicas, multi-zone and multi-region

Operability

  • Health checks on each service
  • Enterprise observability and alerting
  • Reviewed, numbered releases
  • Live uptime checks and incidents
  • Tamper-evident audit trail

Compliance

  • Audit-ready for SOC 2 and ISO 27001
  • Aligned with ISO 27017, 27018 and 27701
  • GDPR export and erasure
  • Regional placement in the US or EU
  • Terms and Privacy per region
Review securityCompliance status
Common questions

Questions buyers ask about SynaptaGrid Platform

What is SynaptaGrid Platform?

SynaptaGrid Platform is a managed multi-tenant platform for B2B SaaS companies. It is the foundation a software team uses to build, launch, sell, operate and keep developing its own SaaS product: development tools and reusable components; organizations, permissions, plans, checkout, subscriptions and invoicing; shared services such as audit, notifications, files, support and AI access over MCP; and the operation of that platform layer on AWS.

Who is SynaptaGrid Platform for?

B2B software companies with a live product whose next enterprise customer asks for single sign-on, SCIM provisioning, an audit trail, EU data placement or contract billing. Teams building a new SaaS product can build on it from the start, and a business without engineers can have the application built for it.

What does my team still build?

Your product: the business rules, screens and experience your customers pay for, plus connecting them to the platform through the App SDK and APIs. The platform supplies the accounts, access, billing, shared services and operations around it. If you prefer, we can build the application for you.

Can our customers sign in with their own identity provider?

Yes. Customers sign in with their own identity provider over OIDC or SAML, and their IT teams can provision and remove people with SCIM. Your operators sign in to the operator console separately.

How do our customers pay?

Customers choose a plan and pay through Stripe or Paddle. The platform creates their workspace, applies the plan’s features and limits, and handles invoices and failed payments. You change what each plan includes without deploying your app.

Where does it run, and where is customer data kept?

The platform runs on AWS. Production runs in the United States today, and a customer whose data must stay in Europe can be placed in the EU region. A large customer can be moved to its own database.

Can a customer get dedicated infrastructure for its apps?

Yes, app by app, and you sell it, whether the customer needs it for scale or to meet an isolation requirement. Each app a customer runs can have its own database server, compute, Redis cache and Kafka cluster, included in a plan or bought as a monthly add-on. Once the payment is confirmed the platform provisions the resources and moves that app onto them. Upgrades, downgrades, cancellation and the end of a paid period move the app between shared and dedicated resources and remove what is no longer paid for.

Will it scale as our customers grow?

Yes. Every service runs on AWS with auto scaling that adds and removes capacity as CPU and memory load changes, between a floor and a ceiling set for that service, and scheduled scaling for known quiet hours. A busy service can move to larger tasks, and services run on Fargate, EC2 or Spot capacity. A heavy customer can get its own workers and database, and read replicas spread database reads. These settings live in the reviewed deployment configuration, and each change is previewed before it is applied.

Which security and compliance standards does it support?

The platform is audit-ready for SOC 2 and ISO 27001 and aligned with ISO 27017, 27018 and 27701, with GDPR export and erasure built in and a tamper-evident audit trail. The Trust Center shows the current status of each.

Can AI assistants use our product?

Yes. Your app declares actions as tools, and a customer’s AI assistant can use them over the Model Context Protocol (MCP) with the signed-in user’s permissions. The customer admin decides which tools are enabled.

How is it priced?

Each deployment is quoted from your expected customers, environments and support needs. Building or integrating your application is scoped separately. Book a demo or ask for a deployment assessment to get the inputs for a quote.

Leave the wheel to the platform professionals.

Bring the enterprise requirement holding up your next release. We’ll review what you already have, what the platform supplies and what your team would connect, then prepare the inputs for a quote.

Book a demoGet a deployment assessmentBuilding something new? Find your path →