Monetization

Open core builds trust. Paid operations fund reliability.

The core should stay inspectable and useful. Paid paths should fund support, managed operations, signed builds, appliances, MSP tooling, and enterprise support without weakening local control.

Community

Open Core

Self-hosted

Local gateway core, docs, community runbooks, and inspectable policy model.

Funding

Voluntary

Maintenance, hardware testing, security review, docs, and public roadmap notes.

Operators

Support

Scoped

Guided install, upgrades, recovery review, and policy guidance without traffic inspection.

Appliance

Signed Builds

Waitlist

Signed image or configured device with validation, backup/restore, and optional support.

MSP

Pilot

Design partner

Templates, runbooks, fleet guidance, support boundaries, and repeat deployment workflows.

Keep open

Local gateway core, policy model, DNS and routing primitives, basic UI/CLI, docs, examples, and baseline runbooks.

Charge for

Managed fleet service, hosted backup/status, support bundle review, signed builds, SLAs, MSP tooling, and integration help.

Paid-path proof

Commercial paths should fund operational reliability, not hide the core.

Redacted Gateway dashboard showing route, DNS, tunnel, device, and backup status cards — Support **Review active posture.**
Supports paid guidance without making support the traffic owner.

Redacted Gateway backup and recovery screen — Appliance **Fund recovery reliability.**
Supports signed builds, backup/restore help, and recovery review as paid operational value.

Redacted Gateway routing policies screen — MSP **Package repeatable policy work.**
Supports templates, runbooks, and fleet guidance while keeping policy visible.

Next action

Start with sponsorship, then check launch readiness.

Sponsorship funds the public core; support requests buy operational help without handing over traffic control. Use launch status to confirm the commercial path still matches the public launch gate.

Sponsor Request guided setup Open launch status