Atlas

Philosophy

Not mocks. Not fakes. Not stubs.

A stateful simulation engine that speaks the provider’s language, keeps living state, emits real signed webhooks, and can be steered by tests, staging, or an agent.

Wire-compatible Point base URLs at Atlas. Keep your real client code.
Stateful Order → payment → refund share one world.
Deterministic Virtual clock. Replayable scenarios. Seedable IDs.
Chaos-native Delays, duplicates, failures, and rate limits are APIs.

The wall every team hits

Sandboxes burn time. Mocks burn confidence.

Live sandboxes

Slow, flaky, rate-limited, sometimes paid. Hard to force a 42-second delay or a duplicate webhook on demand.

Mocks & stubs

Too dead. No shared state across calls. No webhook lifecycle. No “fail three times, then settle.”

A living twin of the outside world — under your control, speakable by agents, boringly reliable in CI.

Capabilities

A control plane for the outside world

One engine. Provider plugins. Chaos as a first-class citizen.

01

Scenario engine

Author deterministic journeys as data. Run them from CI, CLI, or MCP.

02

State machines

Orders, payments, conversations, and receipts progress with real provider semantics.

03

Event bus

Append-only history of everything that happened inside a workspace.

04

Webhook dispatcher

Signed callbacks your real handlers accept — Razorpay HMAC, Meta hub signatures.

05

Time simulation

Advance a virtual clock. Flush delayed webhooks without waiting in real time.

06

Failure injection

Fail the next N payments. Delay, duplicate, or drop the next webhook by event name.

Providers

Twins you can point at today

Phase 1 + 2 ship Razorpay and WhatsApp twins deep enough for Sociatribe. The framework is built for many more.

Live through Phase 2

Razorpay Simulator

Orders
Payments
Refunds
Payment links
Signed webhooks
Delays · retries · failures

Live through Phase 2

WhatsApp Simulator

Templates
Conversations
Inbound & outbound
Delivery & read receipts
Rate limits & failures
Interactive replies · flow submissions

Agent-native

Ask the simulator. Don’t click through a UI.

Coding agents and humans share one control plane — MCP tools over the same API CI uses.

atlas · mcp · workspace demo

# Natural language → control plane
› Create three failed Razorpay payments,
  delay the payment.captured webhook by 42 seconds,
  send a duplicate callback,
  then verify the order eventually settles.

✓ fail_next ×3 applied
✓ webhook.delay 42000ms on payment.captured
✓ webhook.duplicate armed
✓ order_00000001 → paid
✓ clock.advance(+42s) · 2 signed captures delivered

How it works

Same client code. Different destination.

Run Atlas Local process or CI service on port 4400.
Retarget base URLs RAZORPAY_API_BASE_URL and WHATSAPP_GRAPH_BASE_URL point at Atlas.
Steer with chaos Control API, CLI, or MCP injects failures, delays, and duplicates.
Assert reality Your real webhook handlers receive signed payloads. Scenarios verify outcomes.

What’s coming

A map that keeps expanding

Atlas is an independent product. Sociatribe is customer #1 — not the ceiling.

Phase 1

First live slice

Core engine · Razorpay · WhatsApp · Control API · CLI · MCP

Shipped

Phase 2

Deepen the twins

Subscriptions · Flows encryption · checkout.js · settlements · scenario packs · SQLite · compose/bootstrap

Shipped

Phase 3

Productize

Stripe · Telegram · Slack · hosted cloud · inspect console · scenario marketplace

The long map

Google Calendar · Gmail · Shopify · SES · Twilio · whatever your stack glues to

Horizon

Stripe
Telegram
Slack
Google Calendar
Gmail
Shopify
SES
Twilio

Get started

Spin up a twin in under a minute

git clone https://github.com/TechBuiltBySharan/atlas.git
cd atlas
pnpm install
pnpm test
pnpm dev
# → http://127.0.0.1:4400

View on GitHub Read the vision Consumer guide

Atlas is a simulation platform — not real money, not Meta production. Point staging and tests at it. Never production payment traffic.

Every external dependency, replaceable with a living twin.