Frequently asked questions.
Answers to the questions we get most often about self-hosting, pricing, and how Visiyon platforms work.
Is Visiyon really free to self-host?
Yes. The core platform is published as open-source software, and self-hosting it costs nothing beyond your own server or VPS. There is no feature-limited "community edition" — the self-hosted version runs the same code as our cloud deployment. What you pay for with an enterprise plan is deployment help, direct support, and additional access-control features on top of that same open core, not a better version of the base software.
What's the difference between the cloud version and self-hosting?
The cloud version at ai.visiyon.com is a managed deployment we run and maintain — you sign up and start using it immediately, with no server to manage. Self-hosting means running the same open-source software on your own infrastructure, which takes more setup but gives you full control over where your data lives and how the platform is configured.
Which AI models can I use?
Visiyon isn't tied to a single model provider. You can connect hosted providers such as OpenAI or Anthropic using your own API keys, or point the platform at a self-hosted inference backend for full local control. Multiple providers can be active at once, and access to specific models can be restricted per team or user group.
Can I use Visiyon for a team, not just myself?
Yes — this is one of the main reasons the enterprise tier exists. Team deployments typically add SSO through an OIDC provider, per-group model permissions, and a shared admin panel for managing users, models, and custom tools centrally rather than per individual account.
What happens to files I upload?
Uploaded files are used to answer the request they're attached to and are automatically deleted after 3 days. Full detail on data handling is in our Privacy Policy.
Can I connect Visiyon to my own internal tools?
Yes. Visiyon supports custom tool/function calling, so a model can call an HTTP endpoint you define mid-conversation — for example, to look something up in an internal ticketing system or a company knowledge base. This is configured per deployment rather than being a fixed integration list.
Is the source code actually public, or just parts of it?
The full core platform is published in the open — there's no hidden proprietary core that self-hosters are missing out on. Enterprise features are additive (deployment support, access control extensions), not a locked-away "real" version of the product.
How do I get help if something breaks?
For self-hosted, community deployments, the best place to start is the GitHub repository — issues, discussions, and the wiki cover most common problems. Enterprise customers get direct support from the team building the platform. You can also use the "Need help?" chat widget on this site for quick questions.
Where can I see what's being worked on next?
Our roadmap and release history are tracked publicly — see the Releases section and the GitHub repository for in-progress work and upcoming changes.
Still have a question?
Reach out through our contact page, or open an issue on GitHub for technical questions about the open-source core.