The build
Built in one weekend. By AI.
Eurora is built by Taiga, an AI software factory. Nobody typed a line of it. This is the log of the first weekend, with times.
The build
Eurora is built by Taiga, an AI software factory. Nobody typed a line of it. This is the log of the first weekend, with times.
01 The estimate
Before anything was built, the factory wrote the plan a conventional programme would need: eleven chapters, from product to verification. Its own arithmetic for doing the job with people:
The arithmetic holds. We kept the plan and changed who does the work.
02 The weekend
From the first commit on Saturday afternoon to the 22nd merge on Monday morning. The infrastructure took ten hours: 21 pull requests between 01:46 and 11:38.
| Helsinki time | What merged |
|---|---|
| Saturday 14 November | |
| Repository created. | |
| The plan: eleven chapters, from product to verification. | |
| Monday 16 November | |
| Infrastructure state store on UpCloud, versioned and locked. | |
| Fix : transport settings the provider actually supports. | |
| Fix : stable policy metadata. | |
| Private network and a database closed to the internet. | |
| Application server in Helsinki: encrypted disk, key-only access. | |
| Fix : boot disk created together with the server. | |
| Fix : remote access comes up on first boot. | |
| Public DNS under management. | |
| Certificates issued and renewed automatically. | |
| A separate database role for every service. | |
| A restricted operator for file versioning. | |
| Private recovery storage in Stockholm. | |
| Addresses for per-account browser isolation. | |
| Certificate challenges delegated to a dedicated zone. | |
| Wildcard certificates for account origins. | |
| Recovery snapshots encrypted before they leave the server. | |
| Test probes for the recording store isolated. | |
| A database of its own for chat. | |
| Deployment record reconciled with what is running. | |
| Addresses and certificates for chat. | |
| Cleanup credentials scoped to test data only. | |
03 The method
A coding agent is one machine inside the factory. The enterprise needs the factory around the machines: the part that decides what gets built, checks it and keeps the evidence.
For Eurora that was a paragraph: a complete office suite, sovereign, on UpCloud, with an open door for outside AI.
Specification, architecture, security model and a way to verify each claim. Eleven chapters for Eurora, approved by a person before any code existed.
Every change is a pull request. Nothing reaches the main branch without passing its checks and a person’s approval.
What changed, why, which checks ran and who approved. The table on this page comes straight from that record.
Deployment, monitoring and maintenance are part of the same loop. The software is not handed over and forgotten.
AI agents do the work. Your organisation defines the rules.
04 Status
05 Taiga
Taiga is the AI software factory for regulated enterprises and the public sector. Business intent in. Production software out. Fully governed. Eurora is what happens when the factory is pointed at something large.
Eurora arrives at Slush on 18 and 19 November 2026.
You are on the list.
We will email you when your invitation is ready. Nothing else.