Requirements
What you need to run infrapage in production.
Requirements
infrapage is designed to be lightweight and easy to deploy. Here's what you need.
Required
MongoDB
infrapage uses MongoDB as its primary database. Any MongoDB 5.0+ instance works — local, Atlas, or self-hosted.
Three collections are used: `pages`, `integration_secrets`, and `users`.
Runtime
Either Docker (recommended) or a Rust toolchain to build from source.
The Docker image is the easiest way to deploy. Building from source requires Rust nightly and the Dioxus CLI.
Optional
Valkey / Redis
Used for session storage and widget data caching. Without it, sessions are stored in-memory (lost on restart) and widgets refetch on every request.
Any Redis-compatible server works (Redis, Valkey, KeyDB, DragonflyDB).
Zitadel
OIDC identity provider for authentication. Without it, infrapage runs in open mode — all admin endpoints are accessible without login.
Any OIDC provider could work with minor adjustments, but Zitadel is the tested integration.
System Requirements
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 128 MB | 256 MB |
| CPU | 1 core | 2 cores |
| Disk | 100 MB | 500 MB |
| Network | Outbound HTTPS | Outbound HTTPS |
infrapage is very lightweight. The compiled binary is a single executable that serves both the API and the WASM client. Memory usage is typically under 100 MB.
Ports
By default, infrapage listens on port 8080 on all interfaces (0.0.0.0). Configure with INFRAPAGE_HOST and INFRAPAGE_PORT environment variables.