Operations
One place that runs every company.
Operations is our own control room. From one screen, on our own hardware, it watches, keeps, runs and protects the technology behind every company of the Octa HQ incubator.
Every company, one shape
How Operations runs every Fruit.
Octa HQ incubates independent companies, referred to as Fruits. Each Fruit grows from a Seed, and Octa Intelligence is the Seed that runs their technology.
Everything a Fruit runs is a record in Operations: its machines, services, websites, domains and accounts, each with the company it belongs to and the aspects it serves. Each record is checked every five minutes. The orchard on Operations Home shows the whole incubator at a glance: the House at the root, its Seeds on branches, each Seed’s Fruits beneath it, and whether each one answers.
A new Fruit does not start from nothing. It is born into the same shape as every other company, so the moment it is on record, Operations watches it, backs it up and counts its visits like the rest.
Eighteen apps
Everything we run, in one place.
Operations is a set of apps, each with one job. Each has its own icon, drawn to move with what it does.
Watch
- Infrastructure
Every machine, service, site and domain of every company, as a record, checked live.
- Monitor
The machine: processor, memory, disk, network and their trends.
- Power
Battery, temperature and power draw, every minute kept, against our own rules.
- Visits
Every visit to the public sites, read from our own server’s log.
- Alerts & Security
Every alert of the network in one place, and the security posture.
Keep
- Backups
Every backup, and whether it is current; it runs our own hourly backup.
- Data store
The datasets: where each comes from, under which licence, and whether it is all there.
- Servers
The public sites’ servers, their state, and the nightly copy of their data to us.
- Launchers
The keys that start each engine at login and keep it alive.
Run
- Queue & Automator
Commands run one at a time, after a confirm; automations on a schedule.
- Control Panel
The machine’s own commands, in one place.
- Models
The engines behind the aspects and Octa Models: built, tested, used.
- Development
Every piece of work as an event: who, what, how long, the tests.
Reach
- Domains
Every domain: expiry, lock, DNS, checked every hour.
- Mail
The mailboxes and routing of every company.
- Leads
What visitors of the public sites send, gathered in one inbox.
- APIs
The keys we hold and the APIs we offer and call.
- Notifications
Where Operations’ messages go, with quiet hours.
A real example
Octa Models, run by Operations.
Octa Models builds environmental models of real places, and it is the first Fruit of Octa Intelligence. This is how Operations runs it, from the screens of 15 October 2026.
- 01
Its place in the orchard
Octa Models is a Fruit of Octa Intelligence. Its website, its server and its domain are records in Operations, checked every five minutes, so a part that stops answering shows on the first screen.
- 02
Its engines
The Models app shows the engines behind Octa Models: 16 models built, 7 of them for sale, 3 of the 8 aspects with an engine, and 46 tests. A new build of an engine is added to the Queue and run there, and a copy of the old build is kept first.
Operations › Models, 15 October 2026: the engines behind the aspects and Octa Models. - 03
Its website
octamodels.com runs on our own server, behind one front door. Every publish is a new release beside the one in use; the switch happens only when every page has arrived, and the release before is kept. Its enquiries reach Leads, and its visits are counted from the server’s own log, with no cookie and no script.
- 04
Every change, on record
Every piece of work on Octa Models, by a person or an agent, is an event in Development: what changed, who did it, how long it took and whether its tests passed. A publish of octamodels.com is one of those events.
Operations › Development, 15 October 2026: 2,029 events across 83 products, 23 days in a row with a change. - 05
Its data, kept
The Octa Models database is part of the folder Operations backs up every hour, with each copy read back to check it. When a backup cannot run, Operations says so at once.
Operations › Backups, 15 October 2026: the backup drive was away, and the page said so at once: “Needs a look”. Drive names blurred.
Resilience
Built to keep going.
Operations does not assume things work. It checks them, keeps copies, and starts them again when they stop.
Kept alive
Our engines start when the machine starts, and Operations restarts any that stops.
A front door that heals
The web server in front of our sites restarts itself within seconds, and every site is asked every five minutes whether it answers. A change to one site is tested first and rolled back if the test fails; it never takes the others down.
Releases, not overwrites
Each publish sits beside the release in use. Nothing switches until every page has arrived, and the release before is kept to return to.
Backups that are checked
Every hour, only what changed is copied, and each copy is read back to make sure it is the same. Earlier versions are kept for 90 days, the backup drive is never filled past 85%, and a sample is read back every month. Each engine also keeps snapshots of itself, and the public servers’ data is copied to us every night.
Power, watched
Battery, temperature and power draw are kept every minute, against our own rules, so a power cut is a line in the log rather than a surprise.
Honest about itself
When something is behind or away, Operations says so on its first screen. A gap is shown, never hidden.
Security
Secure because it is ours.
Running our own operations is a security choice: fewer outside hands on our systems, and one place that sees all of them.
Ours, end to end
Operations runs on our own hardware, and our public sites on a server we run ourselves. The core of the work does not live on someone else’s platform.
Three doors, no more
Our public server lets in only secure administration, web and secure web. Addresses that guess passwords are shut out automatically, and security updates install themselves.
One account, clear roles
Everyone signs in with one Octa Account. The people of Octa Intelligence may look; only Master, who owns Operations, changes a setting, presses a launcher or shows a key.
Confirm before it runs
A command on our machines runs one at a time, and only after it is confirmed. Alerts & Security reads and records; it never changes a setting by itself.
Keys in one place
Every key and shared secret is listed in one app, with every copy beyond its place flagged. A key is shown or replaced only by Master.
A record of everything
Every action is written to a log that is only ever added to, never edited, so what happened can always be traced.
The pictures on this page are real screens of Operations. Details that would help an attacker are blurred, and the screens that hold keys, addresses and sign-ins are not shown.
What decision are you trying to make?
Tell us about your project and what you need to know. We will tell you whether we can help, what we would build, and what it would cost.
For now, we take on only projects aligned with the Octa Methodology and the work of the Octa HQ incubator.