Traffic you can turn up
Steady, bursty, daily or a spike. One slider multiplies every client while you watch.
System design simulator
Draw your architecture, run simulated traffic through a model of it, and see throughput, latency and failures, component by component, as they happen. All in the browser.
A simplified model running in this page. The app simulates every request.
An illustration of the app, with example numbers.
How it works
Drop load balancers, services, caches, queues, databases and CDNs on a canvas and connect them, or start from a ready-made design.
Press play and traffic flows. Every request is simulated, with its path, its latency and where it waits. Turn the traffic up as far as you dare.
Kill a replica, slow a database, lose a zone, or replay an incident modelled on a public postmortem. Alerts fire, and each component tells you why it gave way.
What is inside
Steady, bursty, daily or a spike. One slider multiplies every client while you watch.
Inject slowdowns, errors, crashes and partitions, or replay incidents modelled on well-known outages, step by step.
Every component explains its ceiling: Little’s law, queueing, pool sizes, what it waits on.
Place components in regions and zones; each hop adds the time light would take in fibre over the distance it covers.
Spot the missing rate limit, the single point of failure, the retry storm waiting to happen.
How much more simulated load a design takes, which component gives out first, and a rough monthly cost from list prices.
Read the numbers
Select any component and it shows its theoretical ceiling, what it is offered now, the queueing behind it and what each request waits on. A busy service stops being a mystery: its connection pool is the limit, and changing it shows the difference straight away.
Twenty connections, twenty requests in flight: the pool is the limit. Raise it, or make each query faster.
See it the way on-call does
Alert rules of the kinds on-call teams use: error rate, saturation, health checks, disk, deadlocks, circuit breakers. A condition has to hold before it fires, so one bad sample never fires an alert, and every incident in the run lands on a timeline you can read afterwards.
For AI assistants
ShardPath speaks MCP, so any assistant that does can build a design, run it, find the bottleneck and answer with the simulation’s numbers rather than a guess.
Who it is for
Open a design modelled on a well-known system, run it, and see what each part does and why it is there.
Explore a design idea in minutes, a cache, a queue, another region, on a model, before the RFC.
Show a retry storm or a hot shard live, then publish the design for anyone to open and run.
Pricing
Use the core of the simulator for free. Pro adds every component, case studies, traces, cost estimates and capacity, and your AI assistant. Cancel at any time.
For trying ideas and learning, at your own pace.
$0forever
No card needed.
Join the waitlistFor exploring bigger designs in depth.
$12per month
Billed monthly.
Join the waitlistFor teams that design together.
Let’s talk
Tell us what your team needs.
Talk to us| Free | Pro | |
|---|---|---|
| Build | ||
| Components | 37 core | All 60+ |
| Components in a design | Up to 20 | Up to 100 |
| Designs in your account | 3 | Unlimited |
| Service mesh | – | |
| Kubernetes and Terraform import | – | |
| Design files in and out (JSON) | ||
| Examples | ||
| Patterns and anti-patterns | 45+ | All |
| Case studies | – | 20+ |
| Built-in experiments | ||
| Record your own experiments | – | |
| Every design in the gallery | Most | All |
| Measure | ||
| Metrics and alerts | ||
| Request traces | – | |
| Design review | The most serious finding | |
| Capacity and repeated runs | – | |
| Cost estimate | – | |
| Share and automate | ||
| View-only links | ||
| Links others can copy | ||
| Publish to the gallery | – | |
| Pictures of a design | PNG, with the ShardPath mark | PNG or SVG, without the mark |
| PDF and run reports | – | |
| AI assistant (MCP) | – | |
Taxes are added at checkout where your country requires them. Your first payment is refunded in full within 7 days if you ask. See the refund policy and the terms.
No. It is a theoretical simulator. What you draw never runs on real servers, and ShardPath never connects to your infrastructure. Each component is a mathematical model of what that kind of component does, and the simulation runs those models in your browser.
It is a discrete-event simulation: every request is simulated on its own. Requests arrive at random, the way independent users would. Each component serves them from a queue, with service times drawn around the figures it is given, and connection pools, caches, retries, timeouts and failover follow rules written from the theory. The same design with the same settings gives the same run.
A few inputs come from public sources: the time light takes in fibre between two places, cloud list prices for the cost estimate, a few published service limits (such as object storage’s request rate per prefix), and the companies’ public postmortems behind the case studies. Everything else, each component’s speed, size and limits, is a default chosen so each example shows its point clearly, and you can change any of it. Nothing is measured from your systems, or anyone’s.
Not exactly, and sometimes not closely. The models follow established theory (queueing, Little’s law, how retries multiply load), so what you see, where a queue builds and which part gives out first, is the behaviour that theory describes for the figures given. A real system adds what no model holds: its own code, hardware, network, noise and ways to fail, so its numbers will differ. Use ShardPath to learn, to reason and to compare ideas; to know what a real system does, measure that system.
No. It never sends traffic anywhere: the traffic is simulated, in your browser, through a model of your design. To test a real system under load, use a load-testing tool on that system.
No. It runs in the browser, and the simulation runs on your own machine in a background thread. Your designs are kept in your account, so they follow you to any browser.
Yes. ShardPath has an MCP server, so Claude, Cursor, VS Code and other MCP clients can build a design, run it, inject faults and read the results.
Free: the core components, most examples and three designs of your own. Pro adds every component, bigger designs, the case studies, traces, cost estimates and capacity, the AI assistant, publishing and reports. See pricing.
Join the waitlist with your email. It is free, and we will email you when your place opens.
ShardPath opens soon. Leave your email and we will tell you when your place is ready.