Dreambase Docs

The four parts of a project

A Dreambase project is composed of four things:

Design — the visual architecture canvas: a drag-and-drop view of your service topology and the data flow between services. See Designs & the canvas.
Details— the project's name, description, and other metadata.
Resources — extra files and content attached to the project: docs, specs, reference material, and anything else that helps describe what you are building. The AI assistant can read these when designing and building.
Services— every component of the system. There is no fundamental distinction between “apps” and “services”: everything is a service.

Owned by an organization

Projects belong to an organization. Members join an organization through a membership with a role (OWNER or MEMBER), and access to a project's designs, services, and deployments is governed by that membership.

How the pieces relate

The Design is where you think; the Services are what you ship. As you place services on the canvas and connect them, you are describing both the architecture and the deployment plan at once. Resources give the assistant the context it needs to fill in the details, and Details keep the project identifiable as it grows.

From project to running system

Once a project is designed, you can run it locally or publish it to a remote environment. The same project can have several environments — for example a local environment for development and a remote one for production — each with its own deployments of the project's services.

Think Docker Compose, but visual

If you have used Docker Compose, the model will feel familiar: a project is a set of services that run together. Dreambase adds the visual design, the AI assistant, and managed platform services on top.