The exos
An exo is a ready platform on which one engineer and AI agents build a whole application: a stack plus an agent layer with rules, tests, environments, login and roles. We have three, for different kinds of applications.
exo1 — Node and React
For B2B portals and business applications: customer and partner portals, back office and workflows.
Usable (v0.1.0). Runs in the cloud in a test environment. Not yet used in a client project.
Read more →exo2 — .NET and Blazor
exo1's design on .NET, for clients and teams who want or already run .NET.
Usable locally (v0.1.0). Not yet in the cloud and not yet used in a client project.
Read more →exo3 — web and mobile
For consumer apps: a web app and a native app for iPhone and Android from the same backend.
Under construction. This page describes what has been decided.
Read more →The status is what our own records show today. An exo is only called proven once a real application has been built on it and the evaluation is written.
On the drawing board
Exos we have designed but not built. They get built when a project needs them.
Sprinting Solo exo4 — AI agents (Python)
Business apps that answer from the company's own documents and act in other systems, with a human approving.
Sprinting Solo exo5 — integration hub (.NET)
Keeps ERP, webshop, CRM and SaaS in sync, with retries and a console to replay failed messages.
Sprinting Solo exo6 — data and reporting (Python)
Data from the business systems, tested metrics and dashboards, embedded in portals too.
Sprinting Solo exo7 — offline field apps
Apps for technicians and inspectors: work orders, checklists and photos that sync when the network is back.
Sprinting Solo exo8 — public self-service
Self-service with MitID and MitID Erhverv, WCAG 2.2 AA and Digital Post.