Your architecture map shouldn't live in someone else's cloud.

An architecture model lists every system, every database and every weak spot you have. Obelisk runs on your servers, so that list stays with you.

Request access See every feature

$ docker compose up -d
 ✔ postgres  Healthy
 ✔ obelisk  Started  migrations applied · :8080
$ curl -s localhost:8080/ready
{"status":"ready"}

Sometimes a vendor, an auditor or a new partner needs to see the map. A share link gives them a read-only view, without an account.

Links stay off until an admin turns sharing on for the organization. Each link can require a password, can include the simulations, and can be revoked at any time.

The Obelisk share dialog with a password-protected, read-only link that includes simulations — A read-only link with a password, served from your own domain.

One binary, one database

Nothing exotic. Postgres holds everything; use the bundled container or your own. The obelisk binary serves the app, the API and MCP on one port, and applies database migrations when it starts, so an upgrade is "replace one file and restart". Run it bare or in its Docker image.

Put your usual TLS proxy in front and set OBELISK_SECURE_COOKIES so sessions only travel over HTTPS. Health and readiness checks are there for your load balancer, logs come out as JSON, and you back up Postgres with the tools you already use.

No internet needed. Every script, font and technology icon comes from the Obelisk server, so it works on an airgapped network. The license key is checked offline, and Obelisk sends no telemetry.

Security your team will sign off on

SAML and OIDC: Connect any SAML 2.0 or OIDC identity provider. Accounts are created on first sign-in, and IdP groups map to Obelisk roles.
Roles and access: Admin, editor and viewer roles, and access limited to chosen landscapes.
Hashed secrets: Passwords, session tokens and API keys are stored as hashes. A database dump holds no live logins.
Locked-down sign-in: Login, sign-up and password reset are rate-limited. Close public sign-up if you only want invited users.
Signed webhooks: Every delivery carries an HMAC-SHA256 signature and timestamp, so receivers can reject fakes and replays.
Audit log: Every change, with who did it: a person or an API key, by name. Landscapes, the organization and its members, accounts, passwords (never the password itself), the license and system admin actions. Every import and export too.

Your data stays portable

Self-hosting only helps if you can leave. Export the whole model as JSON or CSV at any time, and diagrams as PNG or SVG. Import YAML or JSON, or drive Obelisk from your own scripts through the REST API.

Data-residency rules: Finance, health, government, or anywhere the data has to stay put.
No third-party SaaS: When you can't send an inventory of internal systems to someone else.
Already on Docker and Postgres: No new vendor contract, no new kind of infrastructure.
SSO without the upgrade: SAML and OIDC come with every install.

Your architecture map shouldn't live in someone else's cloud.

Share it without opening the doors

One binary, one database

Security your team will sign off on

Your data stays portable

Run Obelisk on your own servers.