Home / Questions & answers
Questions and answers
Arci in brief: what it is, how it differs from vibe coding and AI assistants, which tasks it suits and how a pilot works.
What is Arci?
A platform on which a small business team builds and evolves an application itself, together with AI agents. The application is described by a model, and the platform runs it. What you get is a working system, not a prototype.
How is Arci different from vibe coding?
Vibe coding lets you test an idea in an evening, but every next change can break what already worked, and no one is there to maintain the system or own the risks. In Arci the application is described by a model: every change passes the platform's checks, and build and release go through the platform core, which the agent cannot access.
How is Arci different from an AI coding assistant?
With an assistant, the team and the process stay the same: individual tasks get 20–55% faster, but the project as a whole does not. Arci changes the process itself: the team writes a description instead of code, and more than half of the application is provided by the platform.
Does the application need AI once it is running?
No. AI agents help the team build the application; in production it runs without calls to AI. If a process step needs an AI model, the application calls it through the platform's AI gateway: allowed models, personal data masking, budget and log.
Which AI agents work with Arci?
Claude, Codex, Cursor and others; AI models can be cloud or local. The platform's rules and checks sit in the agent's context, and each agent has its own task, permissions and limits.
How does the platform control changes made by agents?
At the first build step the application model is checked against 50 rules and 131 schemas, and an error stops the build. Then come the linter, unit tests and code analysis in SonarQube. Only a verified release goes to the environment, every release is recorded in the audit log, and any past release can be released again.
Which tasks is Arci suited for?
MVPs and hypothesis testing; digitising routine work — requests, registers, approvals and reconciliations from Excel and email; step-by-step modernisation, when functions of a core system, ERP or CRM move to Arci one at a time; a unified front-office system for web, mobile app, kiosk and bot.
Which tasks is Arci not suited for?
Technologically complex systems: processing, billing, settlement and trading systems with millions of operations and strict speed requirements. These are built with conventional or agentic development, and applications on Arci connect to them through integrations.
How does Arci work with our systems?
Through integrations: via API, queues and files, with retries on failure. Standard adapters and field mapping are configured in Arci; only the most complex ones are written in code. Screens can open inside your systems, and the data stays with you.
Which devices does the application run on?
Web, Android and iOS, self-service kiosks and bots — all on one model. A new screen ships without an application release.
What stack is the platform built on?
Java 25, Spring Boot 4, Apache Camel, OAuth2 and OpenID Connect, OpenTelemetry and Prometheus, MCP; mobile clients for Android and iOS.
How does a pilot work?
A pilot takes 8–12 weeks on one process. In the first week we review the task together. From week two your team builds the solution itself, tests it on its own scenarios and launches it with real users. At the end we look at time and cost together and decide on the next step. We'll name the exact timeline once we've looked into the task.
What do you need from us for a pilot?
A process owner and an analyst; an administrator and a security specialist will be needed for a few days. We provide the platform, team training and second- and third-line support for the whole pilot. The pilot can run on our environment or yours.
Where can I see applications built on Arci?
The demo zone at demo.arci.app is being prepared; the first applications in its catalogue are an office management system and a fuel station network. Until it opens, we show the applications in a meeting.
Let's discuss a pilot for your task.
Tell us which process you'd like to move to Arci. We'll run the pilot on our environment or yours.