ServerHTTP, web and proxy server
Serve, route and protect web traffic on your own hardware.
One web server for your sites, console and services, with encryption, routing and load balancing on your own hardware.
We’ll spend 30 minutes with you on one of your workflows, and you don’t need to share any data.
- Synesis
- Virtual Employees
- Agent Harness
- Opsis
- Origin
- Phylax
- Operations
- Platform services
Sites and routes
One server for the console, the APIs and the reverse proxy
| Site | Routes | Certificate | State |
|---|---|---|---|
| Console | 14 | Renews in 61 days | Serving |
| Product API | 38 | Renews in 61 days | Serving |
| Supplier portal | 9 | Renews in 23 days | Serving |
| Engineering docs | 4 | Renews in 61 days | Serving |
| Model gateway | 6 | Internal only | Private |
Requests per second
1,420
Peak 2,980
p95 latency
38 ms
On target
Errors
0.02%
Below budget
TLS
1.3
Everywhere
- Synesis
- Virtual Employees
- Agent Harness
- Opsis
- Origin
- Phylax
- Operations
- Platform services
Traffic, last 6 hours
Requests and p95 latency
— Requests— p95 latency
Busiest routes
- /api/tasks41%
- /api/records24%
- /portal/parts15%
- /api/search12%
- /console8%
Status codes
2xx 96%4xx 3%5xx under 1%
- Synesis
- Virtual Employees
- Agent Harness
- Opsis
- Origin
- Phylax
- Operations
- Platform services
Route: /portal/parts
Supplier portal · edited by a platform engineer
Match and send
- Path
- /portal/parts/*
- Methods
- GET, POST
- Rewrite to
- /parts/*
- Upstream
- Portal service · 3 instances
- Health check
- Every 10 s
Protect
- Sign-in required
- Supplier role only
- Rate limit · 120 per minute
- Export-controlled parts hidden
- Cache responses
Response headers
Strict-Transport-Security: max-age=63072000
Content-Security-Policy: default-src 'self'
X-Content-Type-Options: nosniff
Server › Sites and routes: sites, routes, upstream services and certificate status. Sample data from Inovagio’s example companies.
Where Server works
Server isn’t named in a step of the onboarding. It is part of the platform every step runs on.
What Server does
Server is Inovagio’s web server and reverse proxy: one cross-platform binary that terminates TLS, serves static sites and the Inovagio console, and balances traffic across your services with health checks and circuit breakers.
TLS at the edge
TLS 1.3 by default with mutual TLS, certificates read from Inovagio Secrets by reference and rotated live without a restart.
Static sites and single-page apps
Range requests, conditional GET, precompressed assets and single-page-app fallback from a configured root.
Health-checked load balancing
Round-robin, least-connections, random and weighted strategies, with active health checks and circuit breakers on every named upstream.
Safe retries only
Idempotent GET, HEAD and OPTIONS requests fail over to the next healthy backend, and nothing else is ever retried.
Trusted upstreams
Upstream TLS verification with custom CA bundles, SPKI pinning and SNI override.
Virtual hosts and caching
Route by path, host or wildcard host, transform headers and paths, and cache eligible responses per route.
Current protocols
HTTP/2 and HTTP/3 to clients, WebSocket and gRPC passthrough, and streaming without full-body buffering in either direction.
Serves the console
Hosts the server-rendered Inovagio console and its backend, so the product needs no separate web runtime.
Operator controls
Config validation, reload without dropping connections, backend drain and undrain, graceful shutdown, and logs, metrics and traces to Panoptes.
Everything Server does, by area.
Serving
- Static files with range requests and conditional GET
- Precompressed and on-the-fly compressed assets
- Single-page-app fallback
- Virtual hosts with wildcard host matching
- Security headers and a content security policy on every response
- Hosting for the Inovagio console
Proxying
- Named upstreams with four load-balancing strategies
- Active health checks
- Circuit breakers
- Retry failover for idempotent requests
- Per-route response cache
- Header, path and query transforms
- Upstream TLS verification, CA bundles, SPKI pinning and SNI override
TLS
- TLS 1.3 minimum
- Mutual TLS for inbound clients
- Certificate selection by SNI per virtual host
- ALPN and OCSP stapling
- Automatic certificates over ACME
- Live certificate rotation
Operations
- Config validation before deploy
- Reload without dropping connections
- Backend drain and undrain
- Admin API on loopback with a credential from Inovagio Secrets
- OpenTelemetry export and structured access logs
- Container-platform ingress and gateway route reconciliation
What Server replaces
Server does the work of these, inside one platform with one identity, one policy and one record:
- Web server
- Reverse proxy and load balancer
- TLS-terminating edge proxy
- Container-platform ingress controller
The controls Server brings
Every Inovagio product keeps the same five commitments, because regulated work needs all five at once.
Security
TLS by default, certificates from Inovagio Secrets, and a hardened request path.
Governance
Routes and access rules come from one configuration.
On the record
Every request can be traced and logged.
Monitoring
Request, latency and error metrics in Panoptes.
Cost per task
One server for the console, the APIs, the gateway and the proxy.
Server in your industry
Server runs the same way in every industry Inovagio serves. See the work in yours.
- Financial servicesBanks, credit unions, lenders and insurersWorked example: Alder Ridge Community Bank · Example company
- Healthcare providersHealth systems, hospitals and physician groupsWorked example: Meridale Health · Example company
- Health plansMedicare Advantage, Medicaid and commercial plansWorked example: Ashgrove Health Plan · Example company
- LegalLaw firms and in-house legal teamsWorked example: Calloway Finch · Example company
- GovernmentState, county and city agenciesWorked example: City of Larkhaven · Example company
- DefenseDefense contractors and their suppliersWorked example: Keelstone Aerospace · Example company
- Finance operationsFinance teams in any industry
For developers: Server at a glance
- Protocols
- HTTP/1.1, HTTP/2, HTTP/3, WebSocket, gRPC passthrough
- TLS
- TLS 1.3 minimum inbound; mutual TLS; SNI, ALPN, OCSP stapling, ACME
- Load balancing
- Round robin, least connections, random, weighted
- Configuration
- One YAML file, validated before use
- Telemetry
- OpenTelemetry traces, logs and metrics
- Container platforms
- Ingress and Gateway API HTTPRoute / TLSRoute
- Platforms
- macOS, Linux and Windows
Server in the platform.
Where Server fits
One platformAgent HarnessAgent harness
Inovagio CLIInovagio DesktopWeb ChatInovagio SDK
OpsisExperience layer
FolioMorphe
Virtual EmployeesVirtual Employee layer
NexusErgon
SynesisKnowledge layer
PerceptionMNEMOS
OriginModel layer
Inference ServerForge
PhylaxTrust layer
AuthInovagio SecretsGuard
OperationsOperations
PanoptesArchon
Platform services (this layer)Platform services
Server (this product)API ManagementConnect
See Server on one of your workflows.
Every project starts with one workflow your people know well, measured against what it costs you today.