PL Book a demo

Obsigen · Architecture

Architecture

Three layers with separate roles. The client's data is stored only in its tenant, GRID processes the task and does not keep its content, and devices connect only to their own tenant.

591 tools

including 19 central1 and 40 tenant-side1 - repo counter

8282 tests

531 backend + 256 frontend + 37 extension + 4 hub

63 languages

with a syntax check after every save

56 s4 per drawing

reading time of an A0 technical drawing in Obsigen Magnify

1371 measurement reports

since Aug 28 - repo counter

1Three layers

TENANTS · DATA IS STORED HERE OBSIGEN EXTERNAL PROVIDERS Client A - Managed Cloud TENANT files · conversations · settings Forge Runtime 1 User browser · phone Client B - self-hosted · cloud data stored here Client C - self-hosted · server room 2 data stored here One client - one tenant. Tenants do not see each other. The browser, Runtime and Forge never connect to GRID. They connect only to their own tenant. turn content Signed Turn result OBSIGEN GRID STATELESS CORE model selection per task collaboration of several models tools and sandbox the test has the last word output gate trained on our own test scenes ZERO DATA RETENTION stateless MODELS · INFERENCE IN THE EEA EEA inference 1 EEA inference 2 EEA inference 3 EEA inference 4 Zero Data Retention in the DPA 3 OTHER SERVICES Web search Zero Data Retention Pages named in the chat 4 Image editing no training - but no zero retention 5 turn flow return channel optional zero retention weaker guarantee n footnote below the figure
A task travels from the tenant to GRID and returns with the result.
  1. Forge and Runtime are optional - you take one, both or neither. Each connects only to its own tenant, and Runtime opens no listening port: it initiates the connection itself.
  2. In a self-hosted deployment in your own server room, the only traffic leaving your network goes to GRID. In the on-premise model, GRID and the models also run in your infrastructure.
  3. We agree the list of model providers with you before the start - any provider you do not accept is struck out. When a provider does not respond, the next one in the queue can take over the task.
  4. When a website address comes up in a conversation, GRID fetches the page. That site receives only its own address, and its owner sees an ordinary visit - this is the only item on the right that is not covered by anyone's contractual commitment.
  5. The only place with a weaker guarantee: the material is not used for training, but the provider does not declare zero retention. The feature can be disabled for the tenant - everything else works unchanged.

Tenant Vault

Tenant

Files, conversations, memory, the company glossary and the document index are stored only in the tenant - on infrastructure dedicated to a single client. Its own database, storage and keys; tenants cannot see each other.

Zero-State GRID

GRID

Selects the models for the task, brings several of them together to collaborate and checks the result before handing it back. It has no database - once the task is complete, it keeps no content.

Edge Link

Devices

Obsigen Forge and Obsigen Runtime connect only to their own tenant - never to GRID. Runtime initiates the connection itself and opens no port.

2Security principles

Six principles that apply in every deployment model - Managed Cloud, self-hosted and on-premise.

01

Signed Turn

Every task is signed on the tenant side. GRID verifies the signature and has no access to the tenant's secrets.

02

Sealed Execution

Code from a task runs in a single-use, isolated environment with no system privileges. When it finishes, the environment disappears along with its contents.

03

Egress Gate

The code execution environment has no direct route to the internet. Outbound traffic passes only through a controlled gate with a list of allowed destinations.

04

Device Fence

On macOS and Linux, Obsigen Runtime works inside an OS fence, and known credential locations are masked before every command. Risky commands require consent on the device.

05

Stateless Core

The shared GRID layer has no database and does not keep task content: it processes the task and returns the result to the tenant.

06

Provider Choice

We agree the list of model providers with the client. When a provider does not respond, the next one in the queue can take over the task.

3Tools and models

59 tools1: 19 central1 and 40 tenant-side1. Execution principle: GRID plans, the tenant executes - tools that touch data run in the tenant or on the device.

Models run at providers in the EEA, with Zero Data Retention written into the contracts. GRID selects them for each task based on measurements - how Obsigen GRID works.

4What leaves the tenant

boundarywhat crosses itwhat is stored on this side
User → tenant questions, files, the entire conversation history everything - files and conversations are stored here, in the tenant
Runtime / Forge → tenant only what you choose to share from your own disk on your side; Runtime and Forge connect only to the tenant
Tenant → Obsigen GRID the content of the turn: the question and the context needed to answer it nothing - GRID is stateless
GRID → models the question and the context of the turn nothing - Zero Data Retention written into the DPA
GRID → search only the search phrase, without files or conversation history nothing - Zero Data Retention written into the DPA, a provider in the EEA
GRID → web pages mentioned in the conversation only the address of the page to be fetched nothing of yours - the site owner sees only that the page was fetched
GRID → image editing the image submitted for editing the material is not used for training, but the provider does not declare zero retention - the feature can be disabled
GRID → tenant the result - the only connection in this direction in your tenant

The full data flow map and the subprocessor register are part of the document package shared once an NDA is signed.

5Full technical documentation

We share the detailed architecture description - topology, identity mechanisms, execution isolation, data flows and the full tool list - with IT and security teams during deployment talks, once a non-disclosure agreement is signed.

Demo · 45 min

See Obsigen on your own example

We show Obsigen live, online, on a document you bring - with no confidential data. Then a quote and deployment on dedicated infrastructure.

Book a demo Let's talk

  1. step 1Demo · 45 minonline, on your example
  2. step 2A one-page quotewithin two business days
  3. step 3Deployment and team starta dedicated tenant and team accounts

Footnotes

  1. build-time counter · 2026-09-28 · built-in tools, as of the build date
  2. test reports 2026-09-06/07 · 2026-09-07 · 531 backend + 256 frontend + 37 extension + 4 hub - automated tests
  3. code review 2026-09-08 · TS/JS · Python · PHP · Lua · Bash · HTML - syntax check after every file write
  4. Magnify report 2026-06 · reading time of an A0 drawing