# Bengal Bytes Studio

> A node canvas for software architecture that validates your design, tests it under load and exports a build-ready bundle for AI coding agents.

Bengal Bytes Studio is a browser-based visual system-design workspace that turns a software architecture diagram into a validated, testable specification. You place clients, screens, API endpoints, services, data entities, databases, auth, roles, background jobs and third-party integrations on a node canvas; the Studio validates the graph, reconnects it against a connection matrix, traces user journeys, models capacity, measures real request latency, and exports a deterministic agent bundle that coding agents can build from.

- Canonical URL: https://studio.bengalbytes.com
- Studio: https://studio.bengalbytes.com/dashboard
- New project wizard: https://studio.bengalbytes.com/new
- Templates: https://studio.bengalbytes.com/templates
- Glossary: https://studio.bengalbytes.com/glossary
- Design system: https://studio.bengalbytes.com/design-system
- Last verified: 2026-11-01

## Key facts

| Fact | Value | Detail |
| --- | --- | --- |
| Node types | 21 | Across 9 categories: clients, screens, APIs, services, data, auth, jobs, integrations and layout. |
| Validation rules | 23 | Error, warning and info codes covering primary keys, routing, roles, secrets and graph hygiene. |
| Agent bundle | 14 files | AGENTS.md, graph JSON, architecture, journeys, OpenAPI, data model, roles, integrations and a task plan. |
| Setup | Zero | No account, no database, no environment file. Projects live in the browser and export as JSON. |
| Load testing | Real | Concurrent requests to a stateless validation endpoint, with p50/p95 latency, throughput and server heap. |
| Export | Deterministic | The same graph always produces the same ZIP bytes and SHA-256 checksum. |

## What it does

### A graph that means something

21 node types across clients, screens, APIs, services, data, auth, jobs and integrations — with a connection matrix that rejects nonsense before it ships.

### Validation with receipts

23 issue codes: missing primary keys, unrouted client-to-database links, role references that do not resolve, secrets pasted into config. Every issue tells you how to fix it.

### Real load tests, estimated capacity

Run concurrent requests against the validation endpoint and watch p50/p95, throughput, error rate and server heap. Then see which node bottlenecks first.

### Journeys you can replay

The canvas finds entry points and traces every hop, from screen to endpoint to service to storage. Replay a journey and the nodes light up.

### An agent bundle, not a screenshot

Export AGENTS.md, a machine-readable graph, OpenAPI, data model, roles, integrations and a dependency-ordered task plan as a deterministic ZIP.

### Zero setup, honest storage

Guest mode: no account, no database, no backend to run. Projects live in this browser; export and re-import JSON to move them anywhere.

## How it works

1. **Answer four questions** — Name the project, pick platforms, choose the requirement flags, and get a starter graph plus a stack recommendation.
2. **Shape it on the canvas** — Drag nodes from the palette, connect them, edit configuration in the inspector. Invalid connections are refused on the spot.
3. **Validate and load-test** — Fix what the validator flags, replay journeys, then run a real request load test and read the capacity model.
4. **Export for your agent** — Download the bundle and hand it to Claude Code, Codex or Cursor. It contains the graph, the specs and the plan.

## Templates

- **Web app** (`web-app`) — Client, screens, endpoints, entities, database and auth. 14 nodes, 20 edges, 4 journeys, 0 validation errors. https://studio.bengalbytes.com/new?template=web-app
- **SaaS (multi-tenant)** (`saas-multitenant`) — Roles, tenant scoping, billing webhooks and background jobs. 26 nodes, 39 edges, 6 journeys, 0 validation errors. https://studio.bengalbytes.com/new?template=saas-multitenant
- **Mobile + API** (`mobile-plus-api`) — Expo client with offline support and a sync endpoint. 17 nodes, 25 edges, 4 journeys, 0 validation errors. https://studio.bengalbytes.com/new?template=mobile-plus-api
- **Desktop admin** (`desktop-admin`) — Tauri client, admin panel, roles and an audit trail. 17 nodes, 25 edges, 6 journeys, 0 validation errors. https://studio.bengalbytes.com/new?template=desktop-admin
- **Internal tool** (`internal-tool`) — Admin-only, no public access, queues for background work. 17 nodes, 25 edges, 6 journeys, 0 validation errors. https://studio.bengalbytes.com/new?template=internal-tool
- **API only** (`api-only`) — Endpoints, jobs, webhooks and no user interface. 24 nodes, 34 edges, 4 journeys, 0 validation errors. https://studio.bengalbytes.com/new?template=api-only

## Frequently asked questions

### What is Bengal Bytes Studio?

Bengal Bytes Studio is a browser-based visual system-design workspace that turns a software architecture diagram into a validated, testable specification. You place clients, screens, API endpoints, services, data entities, databases, auth, roles, background jobs and third-party integrations on a node canvas; the Studio validates the graph, reconnects it against a connection matrix, traces user journeys, models capacity, measures real request latency, and exports a deterministic agent bundle that coding agents can build from. It runs as a single Next.js application and works without an account.

### Do I need an account or a database?

No. Guest mode is the default: there is no sign-in, no database and no environment file to configure. Projects are stored in your browser’s localStorage and can be exported as JSON. A hosted auth mode (Better Auth + PostgreSQL) can be enabled with environment variables, but the product is fully usable without it.

### How is this different from n8n or a diagramming tool?

n8n executes automations, and diagramming tools produce pictures. Bengal Bytes Studio produces a typed GraphV1 document: every node carries a schema-checked configuration, every edge must satisfy a connection matrix, and the graph is executable enough to validate, trace journeys through, load-test and export as specs and an ordered build plan.

### What is inside the exported agent bundle?

A deterministic ZIP with 14 files: AGENTS.md, README.md, OPEN_QUESTIONS.md, .env.example, docs/system-graph.json, docs/architecture.md, docs/journeys.md, specs/screens.md, specs/api.openapi.yaml, specs/data-model.md, specs/prisma/schema.prisma, specs/roles-permissions.md, specs/integrations.md and tasks/plan.md. Identical input produces identical bytes and checksum, so it can be reviewed in version control.

### Does the load test measure my architecture or the server?

It measures the real Next.js process: the Runtime Lab sends concurrent HTTP requests to POST /api/v1/simulate and reports round-trip p50/p95, server handler milliseconds, throughput, error rate and heap/RSS. The capacity report is a separate, clearly labelled heuristic model that estimates per-node utilization and the first bottleneck from the graph shape.

### Which node types are supported?

21 node types in nine categories: clients (web, mobile, desktop, admin), screens, API endpoints (REST, webhook, realtime), services, data entities, databases, caches, storage, auth providers, roles, queues, workers, cron jobs, external services, plus layout frames and notes.

### Is my architecture data uploaded anywhere?

No project is persisted on a server. Projects live in localStorage in your browser. Validation, journey tracing, capacity modelling and bundle generation are stateless endpoints: the graph travels in the request body and the response is not stored. You can export and re-import JSON to move a project between machines.

### Can I export a project and open it elsewhere?

Yes. The dashboard exports a project as a .bbs.json file, and the dashboard imports that file on any machine. The agent bundle is a separate export for coding agents and is downloadable as a ZIP or previewable as a JSON manifest at POST /api/v1/export?format=json.

### Is it free?

Yes. There is no pricing page, no seat count and no account. Bengal Bytes Studio is a private project that runs locally or on your own infrastructure; the public API routes are stateless and require no key.

### What is Bengal Bytes Studio built with?

Next.js 16 App Router, React 19, TypeScript, @xyflow/react for the canvas, elkjs for auto-layout, Zod for schemas and validation, fflate for deterministic ZIP export, and Vitest for tests. The app runs as one process with no external services.

## Keywords

visual system design, software architecture diagram, system design tool, node canvas editor, architecture validation, load test software architecture, agent bundle, AGENTS.md generator, AI coding agent spec, Bengal Bytes Studio

## Machine-readable versions

- https://studio.bengalbytes.com/llms.txt — index for AI agents
- https://studio.bengalbytes.com/llms-full.txt — complete reference
- https://studio.bengalbytes.com/sitemap.xml — crawlable HTML routes
