[ SELF-HOSTED ]
Run the dashboard on your own infrastructure.
For teams whose compliance, procurement, or security policy requires the monitoring dashboard to stay inside their network.
Then, optional $500/year after the first 12 months for continued access to the private repos. Your license keeps running either way.
- Perpetual license to run nightowl-api and nightowl-frontend inside one company
- Read access to the private repos: source you can audit, patch, or fork in place
- Docker Compose bundle, license-keyed
- 12 months of repo access included from purchase
- Standard MSA, NDA, and signed DPA
- Security packet for your audit: architecture, threat model, SBOM
[ SCOPE ]
What's not included.
Self-hosted is the same product as the hosted dashboard, deployed inside your network. Two things aren't part of the tier:
Production support
Self-hosted is a license, not a service contract. We maintain the latest version and ship updates to the repos. We don't backport patches to older versions or troubleshoot your deployment. Source access is included so your team can audit and patch in place.
Custom feature work
Self-hosted ships the same code as the hosted product on the same release cadence. Custom contracts and bespoke features aren't part of this tier; roadmap requests come in through GitHub.
Frequently asked questions
What does $5,000 buy?
A perpetual license to run nightowl-api and nightowl-frontend inside a single company, plus 12 months of read access to the private repos so your team can pull updates as we ship them. The license is yours regardless of renewal: if you stop the $500/yr subscription after Y1, the version on your servers keeps running and you stop receiving new commits.
What does the $500/yr renewal cover?
Continued read access to the private nightowl-api and nightowl-frontend repos. As updates and security fixes ship to the latest version, you can pull them. The price doesn't include support — it's a source-access subscription, not a maintenance contract.
What if I don't renew?
The license is perpetual. The version on your servers keeps running indefinitely. You lose access to new commits and any updates shipped after your subscription ends. Re-subscribing later restores access.
Do you support self-hosted deployments?
Not as part of the license. We maintain the latest version, ship updates to the repos, and answer pre-sales questions about architecture and licensing. Production troubleshooting on your infrastructure isn't bundled in — the source is yours to audit and patch in place.
What changes between hosted and self-hosted?
The agent and your tenant PostgreSQL setup are identical: both plans drain telemetry directly to a database you control, and NightOwl never sees request data. The difference is where nightowl-api and nightowl-frontend run, and where the platform database (users, app configs, license records) lives. On the hosted plan, both run on usenightowl.com. On self-hosted, both move inside your network, so no NightOwl-managed system holds anything about your traffic, users, or app configs.
What about SOC 2, ISO 27001, HIPAA?
NightOwl itself is not certified for any of those yet. Self-hosted moves the software inside your already-audited infrastructure, which keeps NightOwl outside your audit boundary. Architecture documentation and a signed DPA are included to support your reviewers.
Can we audit the source code before buying?
Yes. The agent package is open source. For nightowl-api and nightowl-frontend, a read-only repository is shared under NDA before contract signature. After signing, your team keeps access to the source, with the right to audit, patch, or fork in place inside your company. Redistribution and operating the software as a service for third parties aren't permitted.
Is there a per-environment or per-app cap?
No. The license covers a single company with no internal caps on apps, environments, teams, or dashboard users. The contract restriction is on operating the software as a hosted service for third parties.
What infrastructure does it need to run?
A Docker host with Compose v2, and a PostgreSQL instance for the platform database (kept separate from your tenant database). The footprint is modest. A small VM with 2GB RAM runs the dashboard comfortably. Tenant database sizing depends on traffic and matches the hosted plan.
How do upgrades work?
Releases ship to the private repos as new image tags. Pull the tag you want, update the references in your compose file, and run docker compose pull && docker compose up -d. Database migrations run automatically on container boot. Skipping versions is fine; there's no forced upgrade cadence.
What about backups?
Both databases live on your side and are backed up like any production PostgreSQL. The platform database holds NightOwl's own state (users, app configs, license records) and isn't large; daily snapshots are sufficient. The tenant database holds your telemetry and is the one you already back up on the hosted plan.
Get in touch.
The reply includes a security packet, NDA, and sample contract. From signed contract to a working deployment is usually under a week.
support@usenightowl.com