# Applications

> A modern suite of business apps that arrives working, not as a methodology - ready to run on day one, and shaped to how your company works rather than to how the vendor thinks it should

Source: https://aipril.dev/docs/apps

## A set of applications

The word "platform" usually means: here are the parts, now hire someone to assemble them. That is
not what this is.

This is a **modern suite of business applications**. A sales pipeline. A purchase register. A
service desk. An onboarding tracker. A supplier portal. Installed, working, with their processes,
their screens, their reports and their data model already in place, and available from a catalogue
instead of a delivery project.

## The trade nobody should have to make

Enterprise software has offered the same two options for thirty years, and both are bad.

**Buy the best practice.** A large system arrives with somebody's idea of how a company should
work, baked in hard. Where your operation differs - and it always differs, because the differences
are usually the reason you are competitive - you either change the business to match the software or
pay to customise until the next upgrade breaks it.

**Or build your own.** Now it fits, and you own it: the development team, the maintenance, the
security review, the person who left and took the knowledge with them.

The third option is the one worth having: **applications that are already built, on a foundation
strong enough that changing them is normal.** The process, the fields, the routes, the roles, the
screens are a description you can read and change, sitting on a platform that carries the parts
nobody should be rewriting: the data engine, the ledger, the org structure, access control, the
audit trail.

## What "shaped to your reality" means

Your approval has four steps and the fourth only applies over a threshold. Your warehouses are
organised by owner, not by region. You call it a claim where everyone else calls it a ticket,
and it carries two fields nobody else's has. Your discount policy has an exception for one customer
segment that everybody knows about and no system has ever held.

All of that is describable here, because what an application *is* - its fields, its routes, its
rules, its screens - is a description and not compiled code. So changing it later is an edit and a
new version, not a project with a business case.

And you do not have to describe the look of it in words. The application opens on a **canvas**:
move the blocks, change what they show, pin a comment where something is wrong and settle it with
the people standing next to you. What you move is the application's own definition, so it ships with
the version and nobody has to redo it.

## And people are not the only ones working in it

What makes this a different category: **AI employees work inside the applications, alongside the
people.**

This is not a chat window bolted to the side. An agent has a role in the app, a scope of what it may
see and do, and its actions land in the same history as everybody else's. It watches for the deviations
nobody has time to watch for, prepares what a person will decide, does the routine that never
needed judgment, and escalates what does.

## Where to go next

- [What you get](https://aipril.dev/docs/apps/what-you-get.md) - the level of application this means: what it
  knows on day one, what it is connected to, and what it can reach outside.
- [Built by AI, approved by you](https://aipril.dev/docs/apps/authoring.md) - how an AI assistant turns a request into
  a specification, an AI agent builds it, and where a person decides.
- [Under the hood](https://aipril.dev/docs/apps/under-the-hood.md) - applications as versioned artifacts, the reconciler
  that installs them, and what makes an upgrade safe.

Ready-made ones are catalogued under [Solutions](https://aipril.dev/docs/solutions.md).