FerrisKey on Kubernetes

FerrisKey is designed to run natively on Kubernetes. Choose between two deployment methods depending on your operational needs.

Architecture on Kubernetes

graph TD
    ING[Ingress / Load Balancer]
    API[FerrisKey API Pods]
    WEB[FerrisKey Web UI Pods]
    MIG[Migration Job]
    PG[(PostgreSQL)]

    ING --> API
    ING --> WEB
    API --> PG
    MIG --> PG

A typical FerrisKey deployment consists of:

  • API pods — The FerrisKey backend handling authentication, token issuance, and administration
  • Web UI pods — The React-based admin console
  • Migration job — Runs database migrations on deploy
  • PostgreSQL — The backing database (managed or self-hosted)

Next Steps