NewLive dashboard · technology behaviour from vendor docs · the maths behind every number

Crash-test your architecture
before your users do.

ArchSim is a flight simulator for distributed systems. Draw your stack with real technologies, throw traffic and failures at it, and get a straight yes or no, with the monthly bill.

Open source · runs on your machine · no account, no telemetry

DesignTestResults
…
technology profiles

PostgreSQL to Kafka to serverless

…
ready-made templates

each with scenarios to compare

…
kinds of clients

mobile, web, API consumers, generic

0
bytes leave your machine

local, open source, no account

How it works

Sketch it. Shake it. Ship the one that holds.

Edge
API
Orders DB
Drag, drop, connect from any side
1

Design

Drag in real technologies (PostgreSQL, Redis, Kafka, Kubernetes services, mobile and web clients) and connect them.

Cache outage
2

Test

Send traffic, inject outages and slowdowns, and replay every second like a flight recorder.

Yes, it holds up.

949/s
handled
370 ms
p95
$1,278
per month · AWS
3

Decide

Get a straight yes or no against your objectives, the bottleneck, the breaking point and the monthly bill.

Features

Everything a design review argues about, measured

p95 latency LIVE
212 ms
Utilization by component
Replication lag
840 ms
Lock wait
3.1 ms
Event-loop lag
12 ms

Watch it like production

A Grafana-style dashboard for every run: throughput, latency, saturation and every technology's own signals, replayed live with a synced crosshair.

Utilization73%

ρ = λ × hold ÷ (1000 × slots)

= 438 × 6.7 ÷ (1000 × 4)

Network
Waiting for a lock
Query
Log flush

Show your working

Every number comes with its formula and this run's values, and sampled requests show each hop, wait and lock they hit.

Outage · cache · 20–32 sSlow ×4 · payments+200 ms · edge link
Edge
API
Cache
Orders DB

Break things on purpose

Schedule outages, slowdowns and network latency, then watch every part heat up and recover, second by second.

  • Mobile50%
  • Web35%
  • API15%

Clients from every channel

Mobile apps, web browsers and API consumers share the traffic, each with its own timeouts, retries and network.

1 vCPU 2 GiB

CPU caps it at 196 req/s

CPU 100% busy · memory peak 366 MiB of 2 GiB

Sized like real machines

CPU cores, memory and storage on every part. Too few cores and work queues; too little memory and requests are refused.

Cost against speed

Run every scenario and see which options meet your objectives for the least money.

Replicas ×3 → ×7 → ×3

Autoscaling and serverless

HPA-style autoscaling with start-up delays, serverless cold starts and concurrency limits.

kind: Deployment
replicas: 3
resources:
requests: { cpu: "2", memory: "8Gi" }
limits: { cpu: "2", memory: "8Gi" }
kind: HorizontalPodAutoscaler
maxReplicas: 14

From model to manifests

Export Kubernetes or Docker Compose scaffolding with replicas, autoscalers and resource limits from your model.

Run · seed 42adcdc5aff2…
Re-run · seed 42adcdc5aff2…

Same input, same seed, same result digest. Bit for bit.

Reproducible to the bit

Every run records its input, seed and engine version. Re-run it and get exactly the same answer.

Templates

Start from a working system

Each one comes with scenarios ready to compare. Open it, press Simulate.

Ready to break something?

Open the starter example and press Simulate. Your first answer is seconds away.