<Home>
Start here
← All templates
application / DEPLOYMENT PRESET

Outpost

Self-hosted webhook delivery with separate API, delivery and log workers, plus independently bundled or existing PostgreSQL, Redis and RabbitMQ.

Before you start

  • Persistent PostgreSQL, Redis and RabbitMQ, each bundled or supplied independently
  • Stable API, JWT and AES keys retained with coordinated data backups
  • A dedicated database, Redis keyspace and RabbitMQ virtual host when using existing dependencies
  • Startup applies upstream PostgreSQL and Redis migrations before the server roles become ready
  • Configure tenant-scoped portal authentication and destination delivery rules in your application

Configuration that needs your attention

The API is the only public service. Delivery, log, migration, PostgreSQL, Redis and RabbitMQ remain private; RabbitMQ management has no public route.

An explicit deployment job applies SQL and Redis migrations once per release revision. API, delivery and log services wait for that job and the selected dependencies.

All application processes use the upstream non-root UID 65532. Anonymous registry access is sufficient for every image.

Redis contains tenants, destinations and retry state. Its bundled 64 MiB no-eviction data budget rejects new writes when full; increase capacity before sustained traffic.

Existing infrastructure is not provisioned or deleted by Hakopod. Outpost applies schema migrations and declares its exchange and queues within the resources you provide.

Portal, topic, retry and deployment-ID settings retain upstream defaults. Outpost is an API and embeddable tenant portal, not a standalone administrator account system.

The pinned RabbitMQ service is a single instance; PostgreSQL, Redis and queue volumes are not independent backups. Review upstream upgrades and test restores before changing image versions.

Required secrets

Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.

  • api-key
  • jwt-secret
  • encryption-secret
  • redis-password
  • database-password
  • broker-password

Use this preset

  1. Open the Catalog in your own Hakopod dashboard and select Outpost.
  2. Choose the project, environment, and application name. Set the required values and secret references.
  3. Review the generated configuration, resource requests, networking, and storage plan.
  4. Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.

Read the upstream setup documentation ↗

View native TOML and setup notes ↗

Pinned container image

hookdeck/outpost:v1.6.0@sha256:36ed337bb1edf52b6b0130f87e9eef0b9c03187bfb85d946b4eeab5b7b602a28

The catalog pins this image for reproducibility. Review upstream updates and compatibility before changing it.