Latest News
Introducing Github Sync

Trusted by teams at

Features

levels icon

Layers

Go up and down the stack, from the big picture to the details. Terrastruct allows you to split your diagram into multiple layers, so that you can distinguish each layer of abstraction.
behavior icon

Scenarios

Have you ever tried to explain, “what happens when there's an error here”, or “how would the system handle X”? Terrastruct gives you the power to define scenarios, so that you can model how your system truly behaves.
sequence icon

Live data

Instead of static diagrams that deprecate quickly, enrich your Terrastruct diagrams with live production data. Integrate with popular services like AWS, GCP, and Github to make your diagrams dynamically reflect the state of your systems.
levels icon

Layers

Go up and down the stack, from the big picture to the details. Terrastruct allows you to split your diagram into multiple layers, so that you can distinguish each layer of abstraction.
behavior icon

Scenarios

Have you ever tried to explain, “what happens when there's an error here”, or “how would the system handle X”? Terrastruct gives you the power to define scenarios, so that you can model how your system truly behaves.
sequence icon

Live data

Instead of static diagrams that deprecate quickly, enrich your Terrastruct diagrams with live production data. Integrate with popular services like AWS, GCP, and Github to make your diagrams dynamically reflect the state of your systems.
link icon
Link to files
Supplement your diagram with external resources by linking components to a URL, like a Github repository or another document.
integrations icon
Assets
Large library of developer icons, instant one-click search within the app for images online, or upload your own.
permissions icon
Collaboration
Collaborate live with your teammates. Granular control over view and edit permissions.
powerpoint icon
Export to Powerpoint
Giving a presentation? Present your diagram in Powerpoint.

Plans & Pricing

The designer of a new system must not only be the implementor and the first large-scale user; the designer should also write the first user manual. If I had not participated fully in all these activities, literally hundreds of improvements would never have been made, because I would never have thought of them or perceived why they were important.
— Donald Knuth

Sandbox Tier

Free

3 layers / diagram
Up to 100K metric points
Teams up to 3 seats
Unlimited viewers

System Tier

$20/month/seat

Unlimited layers
Up to 10M metric points
Unlimited viewers & editors
Private diagrams
No attribution logo

Enterprise Tier

$35/month/seat

Unlimited metric points
Priority support
Custom billing & invoicing
Single sign-on (SSO) integration
Data encryption options
Usage analytics
For general inquiries, including enterprise options, please contact us

What customers are saying

"Been looking for this for a long time. Office monitors now show diagrams that visualize our architecture with live states."
Murat M. - Sidebar
"Onboarding has become so much easier with Terrastruct. We just point them to a few diagrams where they can explore our codebase architecture and they understand how everything works together without the months of discovery."
Arno K. - Pacifica
"Terrastruct is the best tool if you're diagramming any software architecture that isn't trivial."
Jeremy T. - Software Consultant

Frequently Asked Questions

There's a wide selection of tools that are excellent for creating static single-image diagrams. Terrastruct is not meant as a replacement for those. When what you're diagramming is simple enough to fit into one image, those tools work perfectly. When what you're diagramming has any complexity or layers, Terrastruct is the tool specialized to handle that. We also integrate with system data to show you dynamic diagrams.

A diagram is split up into multiple layers. Imagine diagramming how a computer handles an instruction. For the top level layer, you might have, among other components, one named "CPU", and that's the right level of abstraction. In this top layer, you might describe how the CPU works with the RAM. However, to add more detail of what happens within the CPU, you can create another layer for the CPU, where you now describe what happens within for the same instruction.

A system handles many different inputs under many different conditions. Defining a scenario lets you show how your system at that particular layer will behave in a given scenario. For example, if you're explaining how a hospital system works, a scenario might be when an extra receptionist is added.

Some scenarios are best explained as sequences. When your API gets an error from the database, what's the chain of events? The first step might show the system's immediate reaction to the error, and later steps show how the error propagates throughout the system.

Please email us at info@terrastruct.com and we'll respond within 24 hours.