FIG. 1.1
Schema Blueprints
Draw tables, keys and grain on a gridded sheet instead of a wall of tabs. Symbols snap to the grid, and DDL plus YAML generate straight from the drawing.
Exports: DDL · YAML · PDF
DWG NO. NB-2026-04 · SHEET S-01
Draft your data architecture with engineering precision.
Nimbus is the drawing board for data teams — model sources, pipelines and marts on a gridded sheet, validate the geometry before it ships, and keep every revision on the record like a proper drawing set.
Section 02 — Features
One sheet of record for your whole stack.
Grid 8pt
FIG. 1.2
Dependency & Lineage Mapping
Every connector is checked against live warehouse metadata, so lineage survives the third refactor. Trace any column from Kafka to the dashboard.
Traces: table · column · job
FIG. 1.3
Versioned Revisions
Each save is an immutable revision. Diff any two versions, branch a proposal, and tag releases the way you tag code — with a sign-off block for reviewers.
History: diff · branch · tag
Section 03 — How it works
From first line to issued drawing.
DWG scale 1:100
STEP 01
Draft
Lay out sources, staging and marts on the sheet. Symbols snap to an 8pt grid and carry real metadata, not just boxes.
STEP 02
Validate
Structural checks run as you draw — orphaned nodes, circular dependencies, grain mismatches and missing owners get flagged on the spot.
STEP 03
Deploy
Publish to the team registry, export YAML to CI, and pin REV A. Everyone works from the same issued drawing.
Section 04 — Field notes
Reviewed and stamped by data teams.
Records: 03
FIG. 4.1
“We retired a 40-page Confluence data model in week one. New hires trace Kafka-to-mart lineage in minutes, and nobody asks which doc is current anymore.”
FIG. 4.2
“The revision log paid for itself in our first incident. We diffed the schema change that broke the pipeline in seconds, not a stand-up.”
FIG. 4.3
“Validation caught a circular dependency between two staging models before it ever reached staging. That check alone justifies the seat.”
Section 05 — Pricing schedule
Priced like a drawing set, not a data centre.
Rates: USD
TIER 01
Draftsman
$0Forever
- 3 active blueprints
- 1 repository seat
- PDF & PNG export
- Community support
Most popular
TIER 02
Studio
$24Per editor / mo
- Unlimited blueprints & branches
- Live lineage mapping
- Revision diffs & sign-offs
- CI validation API
- Priority support
TIER 03
Firm
CustomAnnual
- SSO / SAML & SCIM
- VPC or on-prem deployment
- Audit log & DPA
- 99.9% uptime SLA
- Dedicated data architect
Section 06 — Specifications
Frequently specified questions.
Q.01–Q.05
Q.01Does Nimbus connect to our existing warehouse and orchestrator?
Nimbus reads metadata — never row data — from Snowflake, BigQuery, Redshift, Postgres, dbt and Airflow over read-only credentials. No agents to install, and sheets stay in sync with the live environment.
Q.02Can we export blueprints for docs and CI?
Every sheet exports to PDF with a proper title block, plus SVG, PNG and a versioned, machine-readable YAML. Most teams commit the YAML to git and let CI validate sheets on every pull request.
Q.03How does revision control actually work?
Every save is an immutable revision with author and timestamp. Diff any two revisions, branch a proposal for review, and tag a release — REV 2026.02, say — once it is signed off.
Q.04Is our metadata secure?
Nimbus is SOC 2 Type II. Metadata is encrypted in transit and at rest, SSO/SAML ships with Firm, and the full service can run inside your VPC. We never execute queries against your data.
Q.05Can the whole team work on one sheet?
Sheets are multiplayer: analysts draft, architects review, and comments pin to symbols like redlines on a drawing. Role-based permissions keep the sign-off block honest.
Section 07 — Issue for construction
DWG NO. NB-2026-04 · Approvals pending
Put your architecture on the record.
Request access to the beta review and we'll issue a Studio key within one business day. No credit card, no procurement call.