Architecture - Devias

Devias has three parts: the studio, the server and modules. All clients, including the studio, scripts, workflows and agents, reach the data through the same server.

Parts of Devias

Part	What it is
Studio	The React app people use: tables, boards, record pages, workflows and the assistant.
Server	An HTTP API with a data engine behind it. It stores data in Postgres, checks permissions and announces every change.
Modules	Packages that plug into both sides. A module adds objects, views and actions to the server and screens to the studio.

studio  ──────►  API + data engine  ──────►  database
   ▲                      ▲
   └────────  modules  ───┘

One way in

The studio, scripts, workflows and agents all call the same server. There is no side door: anything the studio can do, the API can do, and the same permission check applies to both. See Access and permissions.

Every change is an event

When a record changes, the server writes an event. Events keep open pages up to date, start workflows, and let other systems follow changes without polling. See Change feed and SDK events.

The studio draws what the data describes

The studio has no built-in knowledge of a “deal” or a “person”. It reads a description of the objects, fields, views and layouts in the workspace and draws whatever it finds. A field added in Settings and a field shipped by a module therefore look and behave identically.

Data model: objects, fields and records.
Modules: how an area of the business is packaged.
Deploy: run the server and the studio.