Platform

Every vendor behind one seam, swappable by design.

Payments, email, SMS, AI, auth, and storage all resolve through a single provider manager. Explore what each category does, which providers plug in, and how they connect along one order.

Seatmap coreCheckout

Money in, routed your way.

Wired to
Checkout
Providers
  • Stripe
  • Offline / box office
  • PIX · iDEAL · UPIOn the roadmap

Six categories, one pattern

Every category follows the same contract: an interface in the core, adapters registered at boot, connections stored per tenant or workspace, and purposes that wire a connection to a job.

Payments

Money in, routed your way.

Checkout charges run through an intent-based payment seam: authorize at checkout, capture once the purchase saga settles, refund with reconciliation. Currency and country routing rules pick the connection per order, and the choice is recorded on the order itself.

Wired to
Checkout
Providers
  • StripeAvailable today

    Payment Element, 3DS/SCA, manual capture, refunds, signed webhooks.

  • Offline / box officeAvailable today

    Cash and comp sales at the door, settled by staff.

  • PIX · iDEAL · UPIOn the roadmap

    Redirect-based local methods on the same intent seam.

Email

Transactional mail buyers actually receive.

Order confirmations, ticket delivery, and sold-seat resolution notices are dispatched per purpose, so each job can run on a different connection, or all of them on one.

Wired to
Order confirmationTicket deliverySold-seat resolution
Providers
  • ResendAvailable today

    Resend-compatible HTTP API, delivering today.

  • More ESP adaptersOn the roadmap

    The adapter contract fits any transactional email service.

SMS & OTP

Codes and alerts on the phone.

Staff MFA codes already deliver over SMS through a channel-aware, swappable seam. Buyer-facing SMS, order and ticket alerts, rides the same notification contract as it expands.

Wired to
MFA codes
Providers
  • TwilioAvailable today

    Twilio Messages API, delivering staff MFA codes.

  • Buyer SMS & pushOn the roadmap

    Order and ticket alerts over the shared notification seam.

AI

One default model per workspace, yours.

AI features resolve a workspace-scoped default LLM connection instead of a platform-wide key. The adapters are real and tested today; the Sox admin assistant plugs into this connection as its backend lands.

Wired to
AI completions
Providers
  • OpenAIAvailable today

    Chat completions adapter, workspace-scoped.

  • AnthropicAvailable today

    Claude adapter on the same contract.

  • Sox assistant backendOn the roadmap

    The admin copilot runs on your workspace connection.

Auth & SSO

Your identity provider, not ours.

Staff and buyer sign-in resolve through workspace-bound connections: enterprise OIDC or SAML 2.0 with SCIM provisioning, social OAuth, or local passwords, chosen per workspace, never hardcoded.

Wired to
Staff sign-inBuyer sign-in
Providers
  • Generic OIDCAvailable today

    Okta, Entra ID, Keycloak, Auth0, any compliant IdP.

  • SAML 2.0 + SCIMAvailable today

    Enterprise SSO with user and group provisioning.

  • Google · GitHubAvailable today

    Social OAuth via platform configuration.

  • LogtoOn the roadmap

    Optional per-tenant managed IdP, federated over OIDC.

Storage

Files on infrastructure you choose.

Chart snapshots and workspace assets live on S3-compatible object storage. Storage is platform-scoped by design. Workspaces never bind their own buckets.

Wired to
Chart snapshotsWorkspace assets
Providers
  • AWS S3 · MinIOAvailable today

    One S3-compatible adapter, cloud or self-hosted.

  • Cloudflare R2Available today

    The same adapter, configured for R2.

One order, every category at work

Follow a single purchase. Each step silently resolves a provider connection.

  1. 01
    Seats heldThe buyer picks seats; the platform holds them in real time.
  2. 02
    CheckoutRouting rules pick the payment connection for the order's currency and country.
  3. 03
    ConfirmationThe order-confirmation purpose fires through the workspace's email connection.
  4. 04
    Ticket deliveryTickets go out over email, with SMS joining on the same notification seam.
  5. 05
    At the doorStaff sign in with the workspace's IdP and MFA to run box office and scan-in.
  6. 06
    Behind the scenesThe AI assistant works over the connection your workspace configured.

How a swap actually happens

No deploys, no rewrites. The resolver walks a fail-closed chain on every call.

The resolution chain

  1. 01Workspace bindingAn ordered chain per purpose. The first healthy connection wins, dead ones are skipped. Your failover list, for free.
  2. 02Workspace defaultNo binding? The workspace's default connection for the category.
  3. 03Tenant sharedConnections shared across workspaces, with an access list.
  4. 04Platform envSelf-hosted defaults from environment configuration.
  5. Fail-closedNothing matches. It stops. Production checkouts never silently fall back to a mock.
Vaulted credentialsSecrets encrypt at rest with envelope crypto, display once at creation, and every decrypt is audited.
Test before it servesConnections are verified from the admin panel before they can serve traffic.
Routing you can readCurrency and country rules are priority-ordered, first-match, and the chosen connection is recorded on the order.

Bring your own stack

Connect your own payment, email, and identity providers in the demo workspace.