Hosting

Enroute is currently self-hosted. Managed hosting is planned.

Image

Images are published at ghcr.io/enroute-sh/enroute for linux/amd64 and linux/arm64. Releases use 0.1.0-alpha.N version tags.

Tag	Meaning
alpha	Current alpha-channel release
<version>	A release version
sha-<commit>	A specific source commit; never reused

There is no latest tag. Channel and version tags may be rebuilt, so use a sha-<commit> tag when you need an immutable image. The image contains the server, enroute-schema, and proto files in /usr/share/enroute/proto. Build enroute-maintenance from source.

Deployment model

Run Enroute on stateless compute with Postgres for metadata and an object store for Git data. Multiple server instances can share those services behind a load balancer. Lambda ingestion is optional.

Configure storage, security, maintenance, and observability before deploying.

Operator responsibilities

• Terminate TLS for the Git listener.
• Authenticate API callers and set the tenant header.
• Protect and rotate the hook signing key.
• Apply quotas, rate limits, and concurrency limits.

Review Limitations before production use.