Test the services your app depends on.
A customer signs up, receives a code, pays, and opens an account. Connect the app to supported test services, run that browser journey, and check the payment, message, callback, and account records it produces.
Payment accepted
payment_intent.succeeded state changedOrder confirmedReceipt sent to test inbox
order_1042Signed callbackWebhook received and verified
Connect a controlled payment path
Exercise supported success, decline, 3DS, subscription, refund, dispute, and callback states with isolated test data.
Read the code your app receives
Create a test identity, read the delivered OTP or magic link, and continue without using a personal inbox.
Inspect the callback result
Advance the supported clock, trigger an event, and inspect the retry or resulting account state before the next run.
Run the services together
Point the app at the Stripe, Twilio, Email, Auth, and S3 clones it needs. Save a snapshot, run the browser journey, and inspect the records returned by each service.
- Five core service clones
- Documented service APIs
- Repeatable snapshots and callbacks
Advance one hourReset snapshot
State changes available to a testpayment_intentpi_test_042
statussucceeded
webhookdelivered
Payment, order, and callback can be inspected together.
run_snapshot.jsonMake callbacks part of the check
After checkout or signup, check the webhook, email, OTP, or storage change that moves the product forward. The final browser page alone cannot confirm that handoff.
- Payment and receipt state
- OTP and magic-link delivery
- Webhook retries and signatures
PaymentsPayments, subscriptions and callbacks
SMS & voiceMessages and verification codes
EmailInboxes and delivery
AuthIdentities and sessions
StorageBuckets and objects
Each Clone implements specific service behavior. Confirm the API paths your app uses.
Keep a small vendor-sandbox check
Use Clones for supported integration paths. If a vendor-specific behavior is outside the catalog, run a separate authorized contract check and label that dependency clearly.
- Clone-backed CI
- Explicit live contract checks
- No hidden vendor side effects
Frequently asked questions
Have a specific workflow in mind?
Talk to us
Is this just HTTP mocking?
No. A clone remembers what your test created: records, clocks, retries and signed webhooks, so one step can depend on the last. The docs list the operations each clone supports.
Which services are included in the core catalog?
Stripe, Twilio, Email, Auth, and S3 are the five core clone services.
How are live side effects protected?
Clone workflows use isolated test services, keeping test payments, messages, and callbacks away from live vendor traffic.
Test your app’s integrations.
Create a free workspace and describe the first flow to test. Or check a public page first, no account needed.
Free during the beta. No card.