Every registered Veyo user gets access to the on-premise edition. Run the full platform on your own infrastructure. Your source code never leaves your control — and your LLMs get direct access to standard BC base code for exact version and locale matching.
The on-premise edition is not a stripped-down version. It's the full Veyo platform running on your hardware.
Your custom AL/C/AL source code is parsed and stored entirely within your network. No code is ever transmitted to external servers. Ideal for ISVs with proprietary IP.
Give your developers and LLMs direct access to the standard Business Central base application code — for the exact locale, version, and cumulative update they're working on.
Run upgrade analysis between any two versions of the standard base application. Compare your current BC version against the target before committing to an upgrade.
The on-premise edition allows you to ingest the standard Business Central base application for any supported version, locale, and cumulative update. This data is stored as system repositories at the organisation level, shared across all projects.
When a developer asks their AI assistant "how does the Sales-Post codeunit work?", the response is grounded in the exact version running in production — not a generic approximation from training data.
For support analysts troubleshooting a client issue, this means the AI can trace through the actual standard code flow for that client's specific BC version and locale, then identify where custom extensions modify standard behaviour.
For consultants configuring unfamiliar modules, the AI can explain how every procedure, event, and table relationship works in the exact version being deployed.
The Orchestrator is a single binary that embeds the Portal, runs the API, and auto-migrates the database. Add the Ingestor as a companion worker.
Run the init command to generate a configuration file. The wizard walks you through database connection, Clerk keys, encryption setup, and license activation.
Start the Orchestrator and it handles everything: database migration, Portal serving, API endpoints, job queue management. One port, one process.
Run one or more Ingestor instances as companion worker daemons. They poll the Orchestrator's job queue, parse files, and write semantic data. Scale by adding more workers.
Same platform, same features, different deployment model. On-premise adds standard BC code access and complete network isolation.
| Feature | Cloud (SaaS) | On-Premise |
|---|---|---|
| Custom code ingestion & analysis | ✓ | ✓ |
| 14 MCP query tools | ✓ | ✓ |
| Portal dashboard & management | ✓ | ✓ |
| Multi-repository projects | ✓ | ✓ |
| Team RBAC & collaboration | ✓ | ✓ |
| Automatic change detection | ✓ | ✓ |
| Standard BC base application access | Coming soon | ✓ |
| Version/locale/CU exact matching | Coming soon | ✓ |
| Source code stays on your network | × | ✓ |
| Offline-capable (after setup) | × | ✓ |
| Self-update via license portal | N/A | ✓ |
| Hosting | Managed by Veyo | Your infrastructure |
The on-premise edition is included for every registered Veyo user. There's no separate "enterprise" tier to negotiate. Sign up, download, deploy.
Licensing is managed through Keygen. Your license key activates the Orchestrator binary and determines your organisation binding. License validation includes a grace window for offline operation — no phone-home required for day-to-day use.
When updates are available, the Orchestrator can self-update by downloading new artifacts from the Keygen license portal. Both linux-amd64 and windows-amd64 binaries are published with each release.
The on-premise deployment consists of two binaries and a PostgreSQL instance:
Every registered user gets the on-premise edition. Deploy today.