OMNIATECHNOLOGYOpen portal

Omnia documentation

A practical map of the platform.

Start with the system model, then move into authentication, domains, delivery, and integration conventions. Documentation reflects the production architecture—not a separate demo environment.

Start with architecture API directory
omnia / platform
$ platform.describe()
✓ 25 application surfaces
✓ 15 isolated API services
✓ PostgreSQL service databases
✓ Caddy TLS edge

Platform architecture

How product frontends, isolated APIs, PostgreSQL databases, and the edge proxy fit together.

Read guide

Authentication

Session, bearer token, OAuth callback, and tenant-boundary conventions.

Read guide

Domain model

Canonical customer, application, API, and technology domains.

Read guide

Release flow

Private GitHub source to atomic frontend and containerized backend deployment.

Read guide

01 · Architecture

Independent products, shared platform discipline.

Omnia separates each customer-facing industry application from its backend service. Services share deployment and security conventions while preserving their own runtime, database, and health boundary.

ApplicationNext.js static delivery
→
TLS edgeCaddy routing and headers
→
API serviceNestJS isolated runtime
→
DatabaseScoped PostgreSQL data

02 · Authentication

Identity is resolved before product context.

Protected API calls use an access token, then resolve the account, tenant, permission set, and active product context. Public catalog endpoints remain explicitly separated from authenticated operations.

Authorization: Bearer <access_token>
Content-Type: application/json
X-Omnia-Tenant: <tenant_id>

03 · Domains

Business and technology have distinct homes.

  • omniadigital.idBusiness identity and public product landing.
  • *.omniadigital.idCustomer portals, industry products, and production APIs.
  • omniadigital.techTechnical identity, documentation, status, labs, and engineering.

04 · Delivery

Private source to controlled production.

  1. 1
    Review and verify

    Build, type-check, and inspect the exact source state.

  2. 2
    Publish privately

    Commit to the designated private repository owned by Omnia.

  3. 3
    Build on the VPS

    Create static frontend artifacts or backend images from the pushed commit.

  4. 4
    Switch atomically

    Replace artifacts only after a successful build, then verify public behavior.

05 · Security

Operational details without exposing secrets.

This site publishes architecture and reachability signals only. Credentials, private environment values, database access, internal logs, and customer data remain outside the public technology surface.

Report a security concern