Find the outage while it is still a diagram
SystemFlow turns your architecture into a model that actually runs. Draw the system, push real traffic through it, and watch which node gives out first - instead of learning it from a customer at 2am.
Part of the GigPlux product family
One system of record for the whole life of your infrastructure
Design, simulation, observability and diagnosis converge on a single model - so the diagram, the runtime and the incident all speak the same language.
Your architecture, as something that runs
Map every service, dependency and edge onto one canvas where each node carries real behaviour. Trace blast radius and see exactly what stops working when a single box goes down.
- Typed node library across compute, data, network and edge
- Dependency and blast-radius mapping from your own topology
- Layout and project state persist, per environment
Stress it before the load finds the weak point for you
Replay realistic traffic against your topology and watch latency, saturation and retries accumulate - while it is still cheap to be wrong. Runs are billed while they run and stop costing the moment you stop them.
- Spikes, ramps and sustained pressure from one config
- Saturation and cascade propagation across dependencies
- Re-run a saved scenario after every architecture change
A second opinion that has actually looked at your system
A Claude-powered reviewer reads the live canvas - nodes, edges and the metrics from your last run - and argues specifics: the single points of failure, the missing cache, the tradeoff you made without noticing.
- Findings scored and explained, not a generic checklist
- Reliability, scaling, cost and security in one pass
- Names technologies and states the tradeoff either way
130 component types, each with its own behaviour under load
A node is not a rectangle with a label. It carries latency, throughput and failure characteristics, which is what makes the canvas runnable. The 22 newest sit in the library while their simulation behaviour is built - searchable, marked coming soon, and not locked behind a plan.
Pay for the compute you actually burn
Simulation and AI analysis draw from a credit balance instead of a flat fee. Designing, editing and opening your work stays free - credits meter the compute, never your architecture.
Billed while it runs, not per click
A run costs an entry charge plus a small amount every 30 seconds it stays up, and stops costing the moment you stop it. Pausing is free; resuming is not a new run.
Heavy runs cost more than light ones
The rate scales with traffic and the size of the system carrying it. 100 requests a second costs about three times the base rate, and the multiplier is capped so a runaway design cannot drain a wallet before you react.
Every movement is on the record
Grants, coupons, ticks, spends and refunds all land in a ledger you can read back, so any charge traces to the run that caused it.
A failed run refunds itself
Charges settle before the work starts and anything that errors returns the credits automatically. Concurrent runs can never overdraw a balance.
Still being built, in the open
32 releases and 123 changes, each written down in plain language - including the ones that were fixes for our own mistakes.
Start free. Pay when production depends on it.
Plans cover seats, retention and access. Simulation and AI compute draw from Flow Credits on top, so the bill tracks what you actually ran.
For individuals modeling and simulating a single system.
- 1 workspace, 1 environment
- Infrastructure Designer
- Traffic simulation
- AI architecture review (chat)
- 7-day metric retention
- Flow Credits, metered per run
For engineering teams running production workloads.
- Unlimited environments
- Real-time monitoring
- Anomaly detection & root cause analysis
- AI architecture reviews
- 90-day retention
- Role-based access control
- Flow Credits, metered per run
- Shared credit balance and coupon codes
For organizations that need custom terms and support.
- Unlimited usage & seats
- Custom data retention
- Custom credit arrangements
- A direct line to the team building the product
- Invoiced billing available on request
Engineered to the standard of the systems it watches
SystemFlow is in beta and we do not claim certifications we have not earned. What follows is the actual posture, stated plainly.
Hardened by default
Strict CORS, a real CSP, rate limiting, constant-time secret comparison, and dependencies pinned and audited on every build.
Encrypted in transit and at rest
TLS everywhere on the wire; storage encryption through our infrastructure providers. Row-level security on the tables that hold your data.
Roles, not shared logins
Role-based access control with staff invites, so who can change a project is a decision you make rather than a password you pass around.
Privacy by default
We collect what the product needs and nothing else. Your data is never sold, and it is never used to train a model for anyone else.
Deletion that actually deletes
Close an account and its data is purged within 90 days, backups included - not archived indefinitely under a different name.
Self-hosting on the roadmap
Docker-based self-hosting is planned, so telemetry can stay inside your own boundary when that is the requirement.
A small team, one direction, no roadmap theatre
GigPlux is a technology company that builds focused software across productivity, collaboration, security, and AI. Every product solves one problem completely. SystemFlow is the one in active development.
Every major outage is obvious in hindsight. SystemFlow exists to make it obvious in advance - model the system, break it in simulation, and fix it before production ever sees it.
We build focused software that earns its place. SystemFlow does one thing completely: it shows you how your infrastructure fails before your users do.
Break it here. Not at 2am.
Model your infrastructure, push it until something gives, and ship knowing exactly which node was going to fail first.