Bengal Bytes Studio is a node canvas for software architecture — clients, screens, APIs, services, data, auth and jobs. Wire it up, validate it, load-test the design, and export a bundle a coding agent can actually build from.
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.
The Studio keeps the whole system in a machine-readable graph, so every screen, endpoint and entity has one source of truth.
Name the project, pick platforms, choose the requirement flags, and get a starter graph plus a stack recommendation.
Drag nodes from the palette, connect them, edit configuration in the inspector. Invalid connections are refused on the spot.
Fix what the validator flags, replay journeys, then run a real request load test and read the capacity model.
Download the bundle and hand it to Claude Code, Codex or Cursor. It contains the graph, the specs and the plan.
Every template is a complete set of wizard answers. Pick one as a starting point, then edit anything on the canvas.
Client, screens, endpoints, entities, database and auth.
Roles, tenant scoping, billing webhooks and background jobs.
Expo client with offline support and a sync endpoint.
Tauri client, admin panel, roles and an audit trail.
Admin-only, no public access, queues for background work.
Endpoints, jobs, webhooks and no user interface.
Built on a typed graph (GraphV1), deterministic export and a stateless API — it runs on one process with no external services.
21 node types across clients, screens, APIs, services, data, auth, jobs and integrations — with a connection matrix that rejects nonsense before it ships.
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.
Run concurrent requests against the validation endpoint and watch p50/p95, throughput, error rate and server heap. Then see which node bottlenecks first.
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.
Export AGENTS.md, a machine-readable graph, OpenAPI, data model, roles, integrations and a dependency-ordered task plan as a deterministic ZIP.
Guest mode: no account, no database, no backend to run. Projects live in this browser; export and re-import JSON to move them anywhere.
The same ten answers are published as FAQPage structured data, so search engines and answer engines can quote them directly.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Open the studio and start designing. Projects are stored locally in this browser; use export / import to move them between machines, and the stateless API handles validation, simulation and bundle generation.