New Architecture Studio
Design your cloud. Break it here, not in production.
Draw your architecture with real regions, networks and subnets. Every change is checked like a real deployment, tested against outages and priced on AWS, Azure and Google Cloud from their public prices.
- 77 cloud services
- 17 tests, from a crash to ransomware
- 3 clouds priced side by side
- 6 regions, Africa included
-
Draw it as you deploy it
Regions, VPCs or VNets, public and private subnets, gateways, peering, VPN, transit hubs: the same building blocks as in the cloud console.
-
Checked like a deployment
Overlapping ranges, a database the internet can reach, a private server with no way out: what would fail there fails here, with the reason and the fix.
-
Tested like production
Peak traffic, crashes, zone and region outages, bots, a disaster recovery drill and ransomware, against your own availability, latency, RTO and RPO goals.
-
Priced on three clouds
A bill line by line from public list prices, data transfer included, on AWS, Azure and Google Cloud. Export the diagram or a full PDF report.
My designs
Sign in to keep your designs in your account. You can try the Studio without an account: your work stays in this browser.
Sign inTemplates
23 architectures that work, ready to adapt: each one deploys as drawn and passes its tests.
- Static website on a CDN A versioned bucket holds the site, a CDN serves it from a city near each visitor. No server to patch, and a bill in dollars, not hundreds.
- Web app on one server The classic start: one server in a public subnet, a managed database in private subnets. Run the crash test to see why it does not last.
- Load-balanced web app Two servers in two zones behind a load balancer, a Multi-AZ database: a server or a zone can fail without your users noticing.
- Serverless API Functions behind a CDN and a key-value table: no server, no network to manage, and a bill that follows the traffic.
- Web app with a cache Redis answers the hot reads in a millisecond and spares the database: several times the traffic on the same database.
- Three-tier e-commerce CDN, load balancer, auto-scaling shop servers, Redis, a connection pooler, Multi-AZ PostgreSQL with a replica, S3 for images and Stripe through NAT. Checkout waits for the card: its p99 is over a second.
- API gateway and containers A managed API gateway authenticates and throttles, then reaches private containers through a VPC link; data in a key-value table reached through private endpoints.
- Asynchronous order processing The API accepts orders in milliseconds and puts them in a queue; workers charge the card and write the order. A slow payment provider no longer slows your site.
- Microservices starter Two services behind one load balancer, each with its own database, talking through an event bus: the smallest microservices setup that stays sane.
- Media upload and delivery Uploads land in a versioned bucket, a queue feeds the transcoders, and the CDN serves the media worldwide with an origin shield in front of the bucket.
- Highly available web platform Three zones end to end: CDN and WAF, a load balancer, an auto-scaling fleet, a Redis cluster, Multi-AZ PostgreSQL with replicas, encrypted backups copied to another region.
- Kubernetes platform A managed Kubernetes cluster over three zones with an ingress load balancer, Redis, Kafka and a document database. Pods take subnet addresses: the /20 subnets leave room to scale.
- Event-driven with Kafka The order service writes its database and publishes to Kafka; a projector builds the read models and the search index from the events. Consumers can stop for an hour without losing a message.
- Hybrid cloud with a VPN Customers reach a public portal; employees reach the intranet through a site-to-site VPN from the office network, whose range must not overlap the cloud one.
- Marketplace with search Listings in a document database, photos on a CDN, a search cluster kept in sync by an indexer behind a queue: the search stays fresh even when the indexer restarts.
- Multi-region active/passive Paris serves, Frankfurt waits with a replica of the database. When Paris goes dark, DNS failover moves your users within minutes, losing seconds of data.
- Global active/active Europe and America both serve their own users, from a global table replicated in both regions. If one region fails, DNS sends its users to the other.
- Hub and spoke with a transit gateway A hub network with the entry point, the inspection firewall and a central NAT; one network per team attached to a transit gateway; the office on a dedicated link.
- Video streaming Video segments served by a CDN with an origin shield, a playback API for catalog and progress, packagers fed by a queue, segments replicated to a second region.
- Cell-based architecture Customers are split into independent cells, each with its own service and database, behind a thin cell router: a bad deploy or a failing database hurts one cell, never all.
- Regulated fintech DDoS protection, inspected traffic, encryption keys, a Multi-AZ ledger replicated to a warm standby region, and immutable backups that survive ransomware.
- Global SaaS on three continents Europe, America and Asia each run the application next to their users; a globally consistent database commits writes in three regions, so losing one loses nothing.
- AI inference platform An API gateway in front of an orchestrator that retrieves context from a vector index, answers from a cache when it can and calls GPU model servers otherwise; documents are embedded asynchronously.
Questions
Will a design that passes here work on the real cloud?
The Studio applies the providers' own rules: address ranges and reserved addresses, subnet sizes, zones required by load balancers and databases, dedicated subnets on Azure, internet and NAT gateways, non-transitive peering, default quotas. A design the provider would refuse fails here with the reason. What it cannot know, such as your application code, stays your part of the job.
Are the prices real?
They come from the public on-demand list prices of AWS, Azure and Google Cloud for each region, including data transfer. Taxes, free tiers, discounts and commitments are not included, so the bill is an estimate of what you would pay without negotiating.
What is free?
The beginner tier: small architectures of up to 10 components, one saved design, the normal-day and crash tests, the bill on three clouds and the PNG export. Each plan unlocks more services, larger designs, more tests and the PDF report.