Docker-compatible host
A Linux host capable of running the Pulse application container and exposing it through your edge.
Self-hosting · Coming soon
Run the signal stack on infrastructure you control.
Pulse is preparing a supported self-hosted distribution for analytics, uptime monitoring, and scoped agent reports. Explore the architecture now; installation packages and release instructions are not available yet.
Pulse overviewSynthetic demo data
Cookie-free defaults for first-party measurement
Docker + PostgreSQL as the deployment foundation
Scoped agent access without direct database exposure
Expected deployment model
A deliberately small operational footprint.
The planned path keeps the application boundary simple while leaving the database, network, backups, and job execution under your control.
- 01
Your edge
Terminate TLS and route the dashboard, tracker, and API traffic on your domain.
- 02
Pulse application
Run the production app container with authentication, job secrets, and provider settings.
- 03
Your PostgreSQL
Keep analytics, uptime, organization, and audit data inside the database you control.
Controlled releases
The expected production flow runs database migrations through a dedicated tool image before replacing the application container. Pulse does not include a built-in scheduler.
What to plan for
You own the infrastructure boundary.
Self-hosting trades managed convenience for direct control. These are the core services and responsibilities the supported path is being designed around.
PostgreSQL
A PostgreSQL instance you operate, back up, monitor, and make available to the application.
Domain, TLS, and proxy
A public HTTPS endpoint for the dashboard, tracker, health checks, and scoped agent access.
External scheduler
Cron, systemd timers, or another scheduler to invoke uptime checks, insights, and report jobs.
See the product today
Explore Pulse without connecting a site.
Public evaluation is not available. The preview notice explains the current invitation-only access boundary.