AI Core
Describe your business. Get an application.
Start with plain words or documents. Approve one Business Blueprint, then let AI Core build your application for web and Android.
Show an employee leave blueprint with proposed screens, roles and workflow, beside the review and approval controls.
One blueprint your team can review
An AI-led interview asks focused questions and turns your answers into one versioned Business Blueprint. In our tests, this took about 13 questions and roughly 10 minutes.
See the whole proposal
Review screens, validation rules and mobile layouts, workflow steps, roles, reporting hierarchy, permissions and integration points.
Approve before anything is built
Your team approves everything at a human review gate before the build starts. Changes can be rolled back.
From approval to a working application
Build on structured data
AI Core creates a normalised database schema on SQL Server, then menus and list pages checked for load. Capacity and caching advice is sized to your server.
Publish on web and phone
The approved application is published for the web and built automatically as a branded Android app. Web uses Vue; mobile uses Flutter. Both run from configuration.
Move complete application packages
Export and import a whole application from the solution package screen in the web app. The package carries the application's logo, so its identity travels with the design. Packages are signed per company.
Use the screen to move a designed application between your company's environments. Run a dry run first. Review the application you are moving and keep its identity clear at the destination. The package screen is available as part of AI Core.
Company boundaries continue to apply as the application moves. Explore Applications to see which designs and records belong to an application and which settings stay with the company.
Your AI keys, your choice
Keep AI access under company control. Company provider keys serve only that company, and their values are never shown. Platform keys are available only to companies the platform allows. A wrong company key fails rather than silently switching. Each AI call records whose key it used.
Gemini and Claude provide structured answers. Calls wait and retry when a provider is busy. On the model routes page, choose the provider and model for each AI task. Application builds recover safely from interrupted runs and simultaneous submissions.
Google Maps keys for web and Android follow the same company and platform rules. Without a key, coordinates and a map link appear. Uploaded documents undergo prompt-injection screening, tested with a 30-document attack set. Secrets stay out of AI input.
Available to try
Beta features are available to trial and pilot customers and may change before general release.
More AI providers — Beta. Try OpenAI, Azure OpenAI and local models through Ollama. These choices extend the provider options beyond Gemini and Claude, which are available now. Keep the provider choice tied to the AI task through model routes.
More databases — Beta. Try MySQL and MariaDB schema generation, Oracle schema generation and Azure SQL Database hosting. These options remain in Beta alongside the current SQL Server choice. Review the available provider and database options when planning your application.
Explore DynamicForm
AI Core · Multi-company SaaS · Security and identity · Branding and app publishing · Company Admin · Applications
Updated 30 October 2026