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.

Next action

Start with sponsorship or guided support.

Sponsorship funds the public core; support requests buy operational help without handing over traffic control.

Sponsor Request guided setup