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.

01 The estimate

What a suite like this normally costs.

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:

to find out whether it is feasible
12 weeks
to general availability
36 to 48 months
for those four years
€55 to 60 million
person-years of work
274

The arithmetic holds. We kept the plan and changed who does the work.

02 The weekend

22 pull requests. 46 hours.

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.

22 pull requests. 46 hours.
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

Humans define. Taiga builds and operates.

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.

  1. People say what they need

    For Eurora that was a paragraph: a complete office suite, sovereign, on UpCloud, with an open door for outside AI.

  2. The factory writes the plan

    Specification, architecture, security model and a way to verify each claim. Eleven chapters for Eurora, approved by a person before any code existed.

  3. Agents build in small steps

    Every change is a pull request. Nothing reaches the main branch without passing its checks and a person’s approval.

  4. Every merge leaves evidence

    What changed, why, which checks ran and who approved. The table on this page comes straight from that record.

  5. The factory runs what it built

    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

What exists today, and what arrives at Slush.

Done

  • The plan, in eleven chapters
  • The infrastructure foundation, running in Helsinki
  • Encrypted recovery storage in Stockholm
  • This website, designed, written and built by AI in a day

Arriving at Slush

  • The nine applications
  • The MCP connection for outside AI
  • The first invitations from the waitlist

05 Taiga

Want software built this way?

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.

  • Taiga AI Oy, Helsinki
  • Rising Star of the Year 2026 at Maria 01, Europe’s largest startup campus
  • Second of 100 in Arctic15’s 100 Innovations Shaping the Future, 2026

Or just join the waitlist.

Eurora arrives at Slush on 18 and 19 November 2026.

We store your email to send your invitation. No tracking, never sold. Privacy notice