Build
Build on AirawatOS
On AirawatOS you build small, self-contained pieces called components, publish them to a shared marketplace, and any agency on the network can install them. The platform handles the hard, repetitive parts — security, data access, delivery, and running your code safely — so you can focus on what your component actually does. You never deploy a new service; you publish a component onto the fixed platform substrate — no new process, no new port.
What you can build
A driver
Pulls data in from the outside world (an API, a file, a satellite feed) and writes it into the shared record book.
An engine
Server-side logic: takes a request, reasons over governed data, and writes a result. The "brains" behind an action.
An app
A user interface — a screen, map, or form — that people use. It acts as the signed-in user, never as itself.
A solution
A ready-to-install bundle of the above, wired together to deliver a whole service to an agency.
There are a few more kinds — agent, model, pipeline, skill — but drivers, engines, apps, and solutions cover most work.
The path, end to end
Every component follows the same short lifecycle. Each step is covered in this track:
- Build it — a small folder with a description file and your code (Anatomy).
- Declare what it may touch — which data it reads and writes, which sites it may call, which secrets it needs (the Clean Room).
- Test it in a safe sandbox — it must pass before it can ship.
- Publish it — the platform checks and signs it, then lists it in the marketplace (Build, test, publish).
- Install & run — an agency installs it; the platform delivers and runs it safely.