The record
Get the full record of the building. Then everything else gets easier.
Atoll is the record-keeper. One file on a server you already own. It reads the devices, keeps every version of everything you are owed, shows what changed, and opens the record to the tools you choose through an API and MCP. Free, open source, fully functional on your network forever.
What the record holds
Every version of every station, with a hash, a time and who delivered it. Compared with the previous one on arrival.
PreviewThe application files for the field controllers, matched to the station by device, so what the controller exposes and what the station pulled in are both on record.
PreviewMechanical, electrical, floor plans, submittals, sequences, commissioning reports, photos. Attached to the site, a building, a floor, or a piece of equipment.
PreviewDevices and objects read live over BACnet/IP, read-only, whether or not the station ever added them.
PreviewEvery confirmation, every answer, every grant of permission, with a name and a time. Nothing overwritten.
PreviewThe artifacts a site should have on file, from whom, how often, and what is late.
PreviewPreview: public code, in the lab build on GitHub or the next one; not a release. Planned: on the roadmap.
Intake with accountability
The part nobody sells. You ask for what you were always owed, and the record shows who delivered and who did not.
- Declare what the building should have. One backup per station on a cadence. The controller file for every device. The drawing set. The sequences. An administrator writes this down once; it is a fact in the record like everything else.
- Every delivery is a receipt. Who, when, hash, size, and the difference from the previous version: setpoints changed, alarms disabled, devices renamed or removed. A page you can read and a file you can forward.
- What is late is visible. An overdue list, by artifact and by who owes it. Not a nag; a ledger.
- Pull where you can. Where a platform documents a way to fetch a backup or an export, Atoll fetches on the cadence so the record does not depend on anyone remembering. Read-only, per platform, after legal review of each vendor's terms.
Preview Public code; in the next lab build
Why contractors should want this
The same record that holds a contractor to a cadence also proves what they delivered, when, and what the station looked like before someone else touched it. Backups you were asked for on a schedule are backups you do not have to recover at two in the morning. A disagreement about who changed a setpoint becomes a diff with a date on it.
Why owners should want this
You own the building. You should own its description. Every platform that wants to sit on top of your building, including ours, starts from a record you control and can take with you.
Several ways in, one record
- Uploaded. The local web page is an intake desk: drop backups, controller files and drawings on it. Upload-only by default; taking an original back out is a separate grant. Preview
- Watched folders. Point Atoll at the station folder on a supervisor and the JACE backups a provisioning job drops there arrive on their own, on a cadence, each one a receipt. A controller file or a drawing riding inside a backup becomes a record of its own. A backups share or a programs folder works the same way. Preview
- Pulled from the devices. Each JACE directly when there is no supervisor, the supervisor when there is one, through whatever that platform documents. Read-only, per platform, after legal review of its terms. Planned
- Read from the network. What the devices say when asked, over BACnet/IP today. Preview
Why upload-only
A record that anyone can carry out is not a record you control. Anyone who may import can add to it. Downloading an original, exporting the whole record, or changing what is expected are grants an administrator gives by name, and every grant is itself on the record.
Yours, in open formats, at any time
One command produces the whole record: the facts as JSON with their provenance, the original artifacts as they were delivered, the receipts, the change reports. No format of ours is required to read it afterwards. If you stop using Atoll, you lose nothing. Preview
Change reports between any two backups come out as a page and as a file, in controls language, not XML: which setpoints moved, which alarms were disabled, which equipment was renamed or removed. Preview
Doors, not screens
The record is useful because other things can use it. A documented API and read-only MCP tools expose the same facts with the same provenance under the same permissions as the person asking. Put whatever you want on top of the building, including an assistant, including nothing. It starts from the truth, on your server. API and MCP design.
On your network. Cloud only if you want it.
Atoll runs on a server, a VM or a small industrial box on site, fully functional with the WAN unplugged. If you want the record mirrored to a cloud instance you also own, or to ours, that is an outbound connection an administrator turns on, and the screen that turns it on says what is sent. It is never required. The promises, with what is implemented and what is planned.
Everyone is building software for buildings. Get the record first.