Real service behavior. Repeatable test conditions.

Test payments, messages, sign-in, and file uploads without using the real service. Clones give your application a controlled partner for each step, so a checkout or onboarding journey can be repeated safely in local development and CI.

Molar Clones
Connected test servicesIllustrative setup
Your applicationOne isolated test environment
SStripePayment state
@EmailVerification & receipts
TTwilioSMS & OTP
AAuthSessions & identities
S3StorageFiles & uploads
SnapshotAdvance timeRestore

Five core services

Run Stripe, Twilio, Email, Auth, and S3 shaped clones in local or controlled environments.

Move time on demand

Exercise expiry, retries, renewals, and delayed delivery with a virtual clock and snapshots instead of waiting for real time.

Callbacks you can inspect

Supported webhook paths include stable event identity, retry behavior, and vendor shaped signatures for realistic callback tests.

Built for complete journeys

A checkout test can create a customer, confirm a payment, advance a subscription clock, and inspect the resulting callback. An onboarding test can create an identity, deliver a verification message, and continue through the application.

  • Deterministic IDs per seed and run
  • JSON snapshots and restore
  • Go binaries, TypeScript SDK, and Playwright fixtures
Go to documentation
Checkout journeyIllustrative workflow
checkout.acme.test
PaymentAcme Pro plan4242 4242 4242 424208 / 28 · Test card
Signed callbackPayment webhookPOST /webhooks/payment signature verified
Order #1042ConfirmedReceipt → test inbox

Start with the core catalog

The five core clones cover the integration paths teams most often need to exercise: payments, SMS and voice, transactional email, identity, and object storage. Contact us about additional fixture coverage.

Talk through your use case
Identity journeyIllustrative workflow
acme.test / sign up
Create accountJoin your workspace
Acme · test inboxVerify your emailYour code is ready to use.
482190
SessionWorkspace readyMember identity verifiedsession_7f24

A few things
you might be wondering.

Have a specific workflow in mind?
Let’s talk it through

Can Clones charge a real card or send a real message?

The clone paths are designed for isolated test traffic. The TypeScript SDK refuses identified live vendor destructive calls before network I/O.

Which Stripe behavior is covered?

The supported vertical slice includes payment methods, declines, 3DS required states, PaymentIntents, subscriptions, invoices, checkout sessions, disputes, refunds, and related webhooks.

How much vendor coverage do I get?

Each clone focuses on supported integration paths and state transitions. Contact us to confirm the API behavior your application depends on.

Explore the clone catalog.

Choose a concrete workflow. We’ll help you get the right setup for your application.