quietgridlabs.com is built with React.
Built with React. Domain registered in 2026.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 6 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 6 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| 1.27.5 | 6 Nov 2026 | |
| Fonts & Icon Fonts2 | ||
| – | 6 Nov 2026 | |
| Translation & Localization1 | ||
| – | 6 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
mx1.timeweb.rumx2.timeweb.runs3.timeweb.orgns2.timeweb.runs4.timeweb.orgns1.timeweb.rugoogle-site-verification=-wckSuvSit_S9ZOVA4wfbsF9zMu7TmscHmsqWi2uLEgyandex-verification: 069e178256988789_globalsign-domain-verification=0ewG46KaIN3pOZzqDr7yU9gbAUzQsbBVdCAoLi3H7av=spf1 include:_spf.timeweb.ru ~allv=DMARC1; p=none; rua=mailto:support@quietgridlabs.comUser-agent: * Allow: / # The favicon and social card must stay crawlable — Google will not show an # icon in search results for a site whose icon it cannot fetch. Allow: /favicon.ico Allow: /favicon.svg Allow: /og.png Sitemap: https://quietgridlabs.com/sitemap.xml # /llms.txt is the same site written for something that reads rather than # crawls. No search engine uses it as a ranking signal and barely any bot # fetches it; it is here because it costs a build step, and because an agent # asked about C4 or about us can take the whole site in one request.
# Quiet Grid Labs > An independent software studio: we build our own products — Viaduct, a C4 > modeling tool with an MCP server — and take on connected systems and AI work > for other people. This site is the company, the product catalogue, and a plain-language guide to C4 modelling written for people deciding how to document an architecture. Product documentation lives on the product's own site, which has an llms.txt of its own: https://c4.quietgridlabs.com/llms.txt ## Products - [Software that moves things forward](https://quietgridlabs.com/): Independent software development studio. Digital products, connected systems and AI-powered experiences. Discover Viaduct. - [Products](https://quietgridlabs.com/products): Explore Viaduct for C4 architecture, Viaduct Desktop for the app on your own machine, and Viaduct MCP for AI coding agents. - [Viaduct — C4 architecture modelling tool](https://quietgridlabs.com/products/viaduct): Viaduct is a visual C4 editor: all four levels on one model, with Markdown, PlantUML sequences, ER diagrams and API details attached to the elements. Live collaboration and MCP for Cursor. ## C4 guide - [The C4 model — a practical guide to C4 architecture diagrams](https://quietgridlabs.com/c4): A practical guide to the C4 model: system context, container, component and code diagrams, what each level is for, when to stop zooming in, and how to keep C4 diagrams current. - [C4 vs arc42 — a template and a notation, not a choice](https://quietgridlabs.com/c4/arc42): How the C4 model and arc42 relate: arc42 is a twelve-section template for architecture documentation, C4 is four levels of abstraction for the diagrams. Where they overlap, how to combine them, and when arc42 alone is too much. - [C4 vs UML vs ArchiMate — which architecture notation to use](https://quietgridlabs.com/c4/c4-vs-uml): How the C4 model compares with UML, ArchiMate and ad-hoc boxes-and-lines diagrams: what each is good at, where they overlap, and how to combine C4 structure with UML sequence diagrams. - [C4 Code diagram — Level 4 explained, and when to skip it](https://quietgridlabs.com/c4/code-diagram): The C4 Code diagram: what Level 4 shows, why it is usually generated rather than drawn, the handful of cases where it is worth committing, and what to use instead. - [C4 Component diagram — Level 3 explained with examples](https://quietgridlabs.com/c4/component-diagram): What a C4 Component diagram shows, how to pick component boundaries, when Level 3 is worth maintaining, and why most teams should draw it for one or two containers at most. - [C4 Container diagram — Level 2 explained (and what a container really is)](https://quietgridlabs.com/c4/container-diagram): The C4 Container diagram: what counts as a container, why it is not a Docker container, how to draw one from production reality, and the mistakes that turn Level 2 into an infrastructure diagram. - [C4 with PlantUML — diagrams as code, sequences and the C4-PlantUML library](https://quietgridlabs.com/c4/plantuml): Using PlantUML for C4 diagrams: the C4-PlantUML standard library, sequence diagrams that stay at one abstraction level, and the trade-offs of diagrams-as-code versus a modelling tool. - [Structurizr alternatives — C4 modelling tools compared](https://quietgridlabs.com/c4/structurizr): What Structurizr does well, where its DSL-first approach costs you, and which C4 modelling alternatives make sense: Structurizr Lite, C4-PlantUML, IcePanel, Viaduct. Written for people already using it. - [C4 System Context diagram — Level 1 explained with examples](https://quietgridlabs.com/c4/system-context): What a C4 System Context diagram shows, who it is for, what belongs inside and outside the boundary, and the mistakes that make Level 1 diagrams useless. - [C4 model tools compared — Structurizr, PlantUML, drawing tools](https://quietgridlabs.com/c4/tools): C4 tools compared: draw.io and Excalidraw, C4-PlantUML and Mermaid, and modelling tools like Structurizr, IcePanel and Viaduct — including desktop apps that keep the model on your own machine. What each costs you over two years. ## Comparisons - [Top 10 visual modelling tools for software architecture (2026)](https://quietgridlabs.com/compare/visual-modelling-tools): A comparison of the visual modelling tools architects use: Viaduct, IcePanel, Enterprise Architect, Visual Paradigm, Archi, Gaphor, StarUML, Archipeg, GenMyModel and Aplas — purpose, strengths, weaknesses and who each one is for. ## Writing - [Journal](https://quietgridlabs.com/blog): Reading notes and short essays from Quiet Grid Labs on architecture, agentic engineering, and the tools we ship. - [Spec-Driven Development for Agentic SE: why vibe coding hits a team wall](https://quietgridlabs.com/blog/spec-driven-development-agentic-se): Brief overview of Spec-Driven Development for Agentic Software Engineering (arXiv:2609.00252): the productivity paradox, SDD as contract substrate, and the harness that governs agents. - [Writing Code vs. Shipping Code: commits up 240%, releases up 30%](https://quietgridlabs.com/blog/writing-code-vs-shipping-code): Brief overview of Writing Code vs. Shipping Code (NBER WP 35275): commit effects by tool generation, attenuation down the production chain, flat marketplace usage, and one agent that shipped to the App Store. ## Optional - [About Quiet Grid Labs — a lab for developer tools](https://quietgridlabs.com/about): Quiet Grid Labs is a small engineering lab shipping focused developer tools. Fifteen years of building systems end to end, from first sketch to the people who run them. - [Contact Quiet Grid Labs](https://quietgridlabs.com/contact): Request Viaduct access, send product feedback, or write to Quiet Grid Labs directly. We answer within one business day.
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |