BONVOYAGE GATEWAY & CONSOLE
BonVoyage Gateway
& optional Console.
A focused gateway and an optional operating interface. One configuration model, with server-side validation and explicit activation.
VERSION 1.0.4 / RELEASED
The essentials in the traffic path.
Route and connect
HTTP/1.1 and HTTP/2, virtual hosts, path and header matching, weighted upstream selection, DNS refresh, and health checks.
Secure the boundary
TLS/mTLS, API-key and JWT validation, trusted-proxy and source-IP policies, bounded request content, and CORS controls.
Contain pressure
Request deadlines, concurrency limits, request-rate limits, retry budgets, circuit protection, and bounded upstream pools.
Observe decisions
Prometheus metrics, access logs, runtime diagnostics, and bounded OTLP tracing. Understand policy outcomes and dropped telemetry.
Manage changes
Author desired-state YAML, validate, preview semantic changes, activate, inspect actual node state, and restore retained snapshots.
Work without the Console
YAML and CLI are free operating paths. Console Free is optional and registration-free. Supported programmatic management and its API documentation are Enterprise scope. The data plane continues serving its active snapshot without a control-plane connection.
BEFORE, DURING, AND AFTER
A configuration change is a lifecycle.
Declare
Prepare a new desired-state document.
Validate
Check the document through the authoritative API.
Preview
Review the artifact and semantic changes.
Activate
Confirm intent, then inspect node results.
Recover
Restore the exact retained artifact.
Rejected does not mean applied.
In the recorded functional test, a listener change requiring restart was rejected. The existing traffic path continued returning HTTP 200 from the same gateway process.
History stays history.
The rejected intent and diagnostics remained unchanged while the operator created a correction. Exact rollback restored retained artifact bytes under a new sequence.
Recorded September 24 functional acceptance. Not a promise that every configuration change is restart-free; use the v1.0.4 release evidence for exact artifact qualification.
Understand snapshots and rollbackBONVOYAGE CONSOLE FREE
See the state. Not just a success message.
These are recorded screens from the implemented Console, not a simulated live dashboard. Guided controls and YAML feed the same validation and activation path.
Console Free 1.0.4 / Recorded test data.
A FOCUSED DATA PLANE
One request. One owning shard.
Fixed shard ownership.
In the v1.0.4 replay, BonVoyage ran 24 Seastar reactor shards assigned across application CPUs 8-31. Request state and shard-local resources are designed around that fixed ownership.
The tested NGINX model.
NGINX 1.30.4 ran 24 workers schedulable within the same CPU set. The replay did not configure worker_cpu_affinity; NGINX supports that option and may be tuned differently for another deployment.
This describes the tested configurations and their execution models. It does not claim that NGINX cannot use CPU affinity, cannot scale, or has a diagnosed internal bottleneck.
OSS TODAY / ENTERPRISE COMING SOON
The gateway stays complete. Enterprise coordinates the estate.
BonVoyage does not reserve basic gateway correctness for a paid tier. The OSS data plane can route, protect, observe and recover from immutable local state without registration. Console Free adds an optional local interface. Enterprise is planned for multi-team and multi-node governance, durable commercial operations and supported integrations.
| Layer | Free standalone offer / available | Enterprise / coming soon | Boundary that remains |
|---|---|---|---|
| Data plane | Apache-2.0 C++/Seastar gateway. It routes, protects and observes traffic independently from an immutable local snapshot. | The same standalone foundation, with qualified bounded extensions for tenant identity, certificate generations, quota leases and metering. | No request-time license, database or fleet-controller dependency. |
| Configuration | Desired-state YAML plus release-matched validate, format, explain, diff, migrate and preview tools. | Shared policy, reusable templates, environment overlays, approvals and promotion. | One versioned gateway contract, not a second Enterprise-only traffic model. |
| Control plane | Standalone Go validation, compilation, snapshot distribution, ACK/NACK, local rollout and exact rollback. | Highly available organization and fleet coordination, durable history and staged rollout. | The active data-plane snapshot keeps serving if fleet control is unavailable. |
| Console | Optional no-cost proprietary Console Free for one installation, without registration. | Organization, project, environment and fleet views with SSO, RBAC, approvals and durable audit. | Console Free is not OSS source and is never required to run the OSS gateway. |
| Management API | The release-matched internal interface is not a supported public endpoint or SDK contract. | Documented compatibility policy, supported API and SDKs, and approved third-party integrations. | This boundary concerns gateway management, not the application API traffic BonVoyage proxies. |
| Host optimization | Read-only topology inspection and a reviewable single-host plan. Normal installation changes no IRQ, CPU, kernel or BIOS setting. | Qualified, authorized apply, verify and rollback workflows, with coordinated multi-NIC, multi-NUMA and fleet drift management. | Host tuning remains optional. BIOS and firmware are never changed automatically. |
| Operations and support | Public metrics, rules, dashboards, release evidence, community issues and optional Release Assurance. | Commercial support, LTS scope, governed diagnostics and fleet analytics. | Basic health, troubleshooting and public security fixes are not hidden behind Enterprise. |
Enterprise is under development. Final capabilities, availability and commercial terms may change before launch. Enterprise does not replace, disable or impose artificial traffic caps on the OSS gateway.
Clear boundaries. No surprises.
Your infrastructure.
Version 1.0.4 provides Ubuntu 24.04 AMD64 packaging and a portable Linux AMD64 OCI archive. Release notes and documentation define the supported platform and distribution terms.
Kubernetes deployment is in scope, but deployment packaging and formal Gateway API conformance are different claims.
Your operating choice.
The OSS gateway can be run and configured through YAML, CLI or the no-cost proprietary Console without a commercial subscription or registration. Supported programmatic management, API documentation and third-party integration contracts are reserved for Enterprise. This concerns gateway management, not the application API traffic it proxies.
Fleet governance, enterprise SSO, AI-assisted operations, and model-aware AI policies are separate future offerings, not hidden promises in the current gateway.
START WITH ONE SERVICE
Your traffic is the real test.
Bring your workload, your policies, and your latency budget.