Skip to content

Application

This is the entry point for the application layer — the services your team actually builds and owns, as opposed to the infrastructure they run on. Each service below is its own document. All of them assume the relevant infrastructure (PostgreSQL, Zitadel, etc. — see the Infrastructure Setup index) is already running.

Services

1. authapi — Auth broker

Sits between your apps and Zitadel: issues JWTs, manages cookies/sessions, and brokers OAuth2 flows. Depends on PostgreSQL and Zitadel.

2. coreapi — Main application backend

Talks to Postgres, SeaweedFS, NATS JetStream, and authapi (via shared PSK). Also passes MQTT connection details through to frontend clients. Depends on PostgreSQL, SeaweedFS, NATS JetStream, and authapi.

Suggested order

1. authapi   ← needs Postgres + Zitadel already running first
2. coreapi   ← needs Postgres, SeaweedFS, NATS, and authapi already running