Independent by design: a customer-controlled runtime
The Vayon AI customer deployment runs in your environment and does not depend on Vayon AI vendor services at runtime. Licensing is offline and signed; there is no online activation and no phone-home for operation.
Govern. Route. Audit.
Customer-controlled runtime
You control the database, model choices and identity integration; Vayon AI runs inside your Customer Environment.
Customer environment
- Employees, developers and business systems
- Vayon AI Customer Deployment
- Organizational identity & knowledge sources
- Internal models & customer-approved cloud connectivity
Vayon AI Vendor Portal
- Customer & commercial management
- Offline license preparation & delivery
- Add-on & support operations
Not part of the customer runtime request path
Vayon AI Marketing Website
- Public information
- Demo & contact intake
Not part of the customer runtime request path
- Customer requests do not travel through the Marketing Website
- Customer runtime does not depend on the Vendor Portal
- Offline signed licensing remains the licensing model
- Approved cloud execution may still require customer-approved outbound connectivity
- No online activation, no phone-home, no self-update dependency
Offline signed licensing
Licensing is issued offline by the Vendor Portal as a signed file and handed off one-way to the customer deployment.
No online activation, no phone-home, no self-update dependency
Operation does not require online activation, phone-home, or a self-update dependency on vendor services.
Internal and approved cloud model connectivity
Connect internal models and approved cloud models. Approved cloud models may require customer-approved outbound connectivity — separate from any runtime dependence on Vayon AI.
Guided setup and readiness
A guided setup/readiness view helps you reach governed AI readiness.
A reference adoption journey
A conceptual path from first connection to ongoing governance — a reference journey, not a claim of fully automated or fixed-time installation.
-
Connect
- Connect internal models
- Configure approved cloud providers where allowed
- Connect organizational identity and key infrastructure
-
Define
- Define sensitivity and policy boundaries
- Define eligible models and use cases
- Configure authorization and egress rules
-
Integrate
- Connect governed chat
- Connect developer tools
- Connect business systems through Integration Clients and APIs
-
Govern
- Review routing decisions
- Monitor usage and metering
- Review safe audit evidence
- Improve policies and model eligibility over time
What is implemented vs on the roadmap
Setup and readiness support is partial. A packaged customer installer, product-managed database provisioning, hardware-sizing guidance and high-availability/disaster-recovery are on the roadmap and are not presented as complete.
A customer-controlled runtime, independent by design
See how the customer runtime runs in your environment with offline signed licensing — no online activation, no phone-home and no self-update dependency for operation.
