Vantiq is the platform for building real-time, AI-driven enterprise applications that run anywhere. From edge devices to cloud infrastructure. This page covers the three things you need to get moving: getting the right access, taking the training in the right order, and knowing where the reference material lives.
1. Get platform access
The Knowledge Base is open to everyone, including guests. Courses, hands-on labs and partner-only material require a Vantiq Community account with Partner access.
If you already have a Partner account
Sign in at community.vantiq.com/login using your partner email.
If you are reading this as a guest
- Contact Vantiq Account Manager to have Partner access applied, or reach us through the Enablement team
- Go to Register / Log In and complete the registration form.
- Under Community Role, select Vantiq Partner.
- Register with your company email address. Partner access is granted by email domain, so a personal address (Gmail, Outlook and similar) will place you in the Guest role.
- Complete your name, company, position and country, choose a password, and accept the consent and confidentiality terms.
- Confirm the validation email that arrives in your inbox.
- And you good to go!
If your account still shows as Guest after registering, contact your Vantiq Account Manager to have Partner access applied, or reach us through the Enablement team.
2. Take the courses. Everyone starts in the same place
All partner training lives in the Vantiq Academy, which is organised into two tracks.
Step one for everyone: the Foundations Course
Whatever your role, begin with the Applications Developer Foundations Course. It is the required first step for every partner and the entry point to every training path. It is free, self-paced, and takes roughly 12 hours:
- 26 short video lectures, all under six minutes
- A quiz after every lecture to confirm comprehension
- 11 cumulative hands-on labs in which you build a working, distributed, event-driven application
- A final exam.
Technical Courses
After the Foundations Course, continue in Technical Courses (On Demand). Choose a role-based training path, or pick individual electives on the topics you need:
- Server Developer — application logic and platform services
- UI Developer — user interfaces and dashboards in Client Builder
- AI Developer — generative AI and AI agents in Vantiq applications
- Architect — designing systems that meet stakeholder requirements
- Administration — server health, monitoring and resource allocation
Sales Training Courses
For business leaders, account managers and pre-sales roles, Vantiq Business Fundamentals builds the commercial picture: what Vantiq is, where it fits, the platform pitch, and recorded demonstrations you can learn from before running your own
- Sales Foundations — For anyone customer-facing: what AI actually is in 2026, what Vantiq actually does, and how to say both out loud in a pitch that survives a technical listener.
- Advanced Sales — For sellers running deals: the use cases, the competitors, and the playbook for qualifying an opportunity, handling resistance, and knowing which deals to walk away from.
- Advanced Presales — For the technical side of the deal: architecture, discovery, and proof strategy — enough to design a solution an enterprise architect will believe and get it running in production, not just demoed.
3. Use the Developer Guides as your reference
The Developer Guides in this Knowledge Base are the written companion to the courses — standards, design practice and architectural guidance from the Vantiq engineering team:
- Introduction to Vantiq Development
- Designing Vantiq Applications
- Server Development Standards
- Client Builder Development Standards
- Introduction to Intelligence in Vantiq Applications
For a short hands-on introduction before you start the course, the Quickstart Tutorial in the Vantiq product documentation walks you through building your first application.
For anything else, use the search bar at the top of the Knowledge Base — it returns an AI-assisted answer drawn from the full documentation set, so a plain question works as well as a keyword.