Frequently asked questions

Any business management application, with its screens, its rules and its access rights: an internal tool, a CRM, management software, or an app that replaces an Excel spreadsheet. Already built on the platform: a recruitment tracker, a leave management tool, a manufacturing workshop, a hair salon.

Yes. You describe what your spreadsheet tracks: its columns become the application's data, with their rules and their access rights. Each person sees only what concerns them, every list has its search and filters, and your data is imported into the application.

You, without being a developer: you tell the agents what you want, in your own words. The platform also works very well with developers, and that is where it is strongest: you have the agents deliver a few features, a developer codes one by hand, then you carry on with the agents. The code stays regular and coherent at every change: agent or developer, each picks it up where it stands, which other AI-assisted coding tools often do not offer.

With no-code, you build an application with visual tools, without writing code. With low-code, you also use visual tools, and a developer writes part of the code. With AIA Studio, you describe the need in your own words, and AI agents write all the code: for you, it is no-code. This code is the application's real code, standard .NET and React, and it belongs to you: a developer can take it up and code a feature by hand, as in low-code. AIA Studio is a French no-code platform, hosted in France.

No. In vibe coding, an AI writes the code as the conversation goes: any request can call everything into question, and nothing guarantees that the application will last. With AIA Studio, the AI does not improvise the code. It describes your application: its data, its screens, its rules and its access rights. The platform then builds most of the code from that description, with proven building blocks, the same way every time. A change alters the description, not the whole application. Every improvement to a building block benefits every application. Tests, code review and penetration tests come on top, with every feature.

An estimate, for a simple application: a hair salon's, with 6 entities (its clients, its services, its team, its working hours, its absences and the appointments), 3 roles and 2 languages, with appointments booked online and the salon's agenda. The base takes half a day: about an hour of conversation with the adviser, then three and a half hours of building. Then come a day and a half of trials and changes, in about 8 features. About 2 days in all.

Yes. No throwaway mock-up: from the first day, you try the real application, the one that will go live.

Through automated tests, a code review, a trial in the browser, a check of every screen on mobile and on computer, and penetration tests with their report.

It speaks French and English.

With our hosting, in France, by OVHcloud. Without it, on your own server. Only the AI can be elsewhere: you choose the model, in France or in the United States.

Yes. Your teams then build and deploy it from its source code, with their own tools. Our hosting, for its part, comes on top of the subscription and is never taken without it: the platform is what puts the application into production, with a backup before every go-live and a rollback possible. It makes the application reachable through its entry point, in HTTPS, and passes it the settings entered in the studio.

We advise it, for security and robustness. The website is open to everyone; the business application holds your clients' data. Kept apart, each has its own system account and its own database, which the other cannot open: a flaw in the website does not reach your data. Each also has its own memory ceiling, its own deliveries and its own penetration tests: a peak of visits does not take the application's memory, and a page of the website changes without touching the application. AIA Studio does the same: the platform and this website are two applications.

You do: standard .NET and React, which your developers retrieve whenever they want, with its whole history. If you leave, a dated exit: notice, transition, retrieval, then erasure attested by a certificate. The platform's common building blocks this code uses remain under licence.

They are kept while the subscription runs, handed to you in an open format, then deleted after the agreed period.

Yes. Invited to the project with the Developer role, they code a feature with their own tools; the platform reviews it, tests it and delivers it.

Every improvement of the platform also benefits the applications already built, at their next change.