SynqDocs
Concepts

Test mode

Synq's sandbox, preview, where you run every flow with test keys, Stripe's test cards, made-up sign-ins and devnet, never real money.

Synq runs a second stage beside production, preview: the sandbox. It is the whole product, the same version or a newer one, with its own orgs, users and keys and nothing shared with production. Run your end-to-end tests there, try a flow before you ship it, or build against Synq without touching your live users.

Test mode, the sandbox and preview are one stage under three names: these docs call it the sandbox, its addresses carry preview- and its emails' subjects [Preview], and its keys are test keys, sk_test_…. Wherever you meet one of them, you're in the sandbox, which no status page watches.

WhatIn the sandboxIn production
Dashboardhttps://preview-dashboard.synq.buildthe dashboard
APIhttps://preview-api.synq.buildhttps://api.synq.build
An issuerhttps://acme.preview-auth.synq.buildhttps://acme.auth.synq.build
API keyssk_test_…sk_live_…
BillingStripe's test mode: test cards, never a real chargereal cards
Sign-insevery way in, plus test sign-insevery way in
Solanadevnetmainnet
Statusno status page: write to supportthe status page

Anyone can sign up in the sandbox, as in production, and making an org there wants a verified email too. Nothing you make in one stage exists in the other: an org, a brand, an app, a key or a user made in the sandbox is made again for production, with its own ids and secrets.

Keys

The management API's keys made in the sandbox start sk_test_, and production's sk_live_, so a key that leaks into the wrong config says where it belongs. A test key works only on the sandbox's API, and a live key only on production's. The account API's tokens come from the brand's issuer in each stage, and an app's client secret is its own in each.

Billing

The sandbox's billing is Stripe in test mode. Checkout and the billing portal are Stripe's own test pages, and no card is charged. Pay with Stripe's test cards: 4242 4242 4242 4242, any future expiry and any CVC, for a payment that succeeds, and Stripe's other test cards for a decline or a card that asks for 3D Secure. A plan bought there is the sandbox's alone.

Sign-ins

Every way to sign in works in the sandbox as in production: email codes and passwords, passkeys, wallets and the providers. Its email is real: a code goes to the address you give, its subject starts [Preview] and its sender's name ends (preview), so nobody mistakes it for production's.

To test sign-ins that depend on a GitHub or Google account's age, type or Workspace, turn on an app's test sign-ins: made-up accounts your tests describe, in the sandbox and on a local stack, never in production.

Wallets sign in on Solana's devnet, and token gates read devnet: use devnet tokens and NFTs there.

What is safe to do

Anything. The sandbox's orgs, users and keys never reach production, its payments are Stripe's test payments, and its tokens are devnet's. Give your test org its own name, and keep its keys and secrets out of your production config: a test key never works in production, and your production users never sign in there.

The quickstart runs against the sandbox the same way: sign up at https://preview-dashboard.synq.build, and use the issuer, client ID and secret it gives you.

On this page