Currently in development

The AI project console for regulated enterprises

An always-on AI agent on a dedicated appliance inside your own network. It watches your projects, flags what is at risk, and answers with a source. No data leaves your infrastructure.

Early access for design partners

Become a design partner For investors
Project inputsAnswer with sources

01 Problem

The problem

Status is collected by hand

Project managers ping owners one by one to find out what actually moved.

Knowledge is scattered

Answers sit across tickets, wikis and documents nobody has time to search.

Cloud AI is off the table

In fintech, banking, healthcare and government, project data cannot leave the perimeter. Existing AI assistants are therefore unusable for these organisations.

02 Function

What the console does

Watches the timebox

It spots stalled items, blocking dependencies and scope that crept in mid-iteration, before the goal is at risk.

Answers with sources

It answers questions about your projects and documentation, and shows what the answer rests on. When it has no basis, it says so instead of guessing.

Says what will fit

Time and budget are fixed, so scope is the variable. The console continuously works out what fits in the timebox and which items will not.

Keeps documentation honest

It flags where documentation no longer matches what the project is doing, and drafts the correction.

03 Sovereignty

It runs on your premises, not in a cloud

The console runs on a dedicated appliance inside your network. The language model, retrieval and index all run locally. It connects to your existing systems through their official interfaces and always acts within the permissions of the signed-in user.

Your data stays in the system you control. The console runs locally; external AI services are not part of the data path.
Local inference
Project content is never sent to an external AI service.
No new data processor
The console works only with systems you already run.
Auditable
Every question, source, proposal and approval is logged permanently.
Resilient to device loss
Disk encryption, remote key revocation and fast recovery onto a replacement unit.

04 Control

You decide what it may do on its own

A regulated organisation will not deploy an agent that writes into its systems unsupervised. The default is therefore conservative.

  1. Level 1

    Acts on its own

    Reads project state, sends reminders within approved templates, and assembles briefs.

  2. Level 2

    Proposes, you approve

    Comments, status changes and new items arrive with a preview of the exact change and wait for a click.

  3. Level 3

    Never on its own

    Closing work, moving deadlines and reassigning people always stay with a human.

We do not measure people.

The console evaluates work, not individuals. It produces no personal performance metrics and never reports pace by name.

05 Hardware

Built for NVIDIA® DGX™ Spark

The console is designed for the NVIDIA DGX Spark appliance. The language model, embeddings and vector index all fit on a single unit sitting in your own rack. Spare capacity on the appliance can also scan read-only backup copies.

Member of NVIDIA Inception

ExCoLabs is a member of NVIDIA Inception, a programme supporting startups working with accelerated computing. Membership gives us access to technical resources and preferred terms on the hardware the console is built for.

06 Status

Where we are today

The console is in development. We have a complete product specification, the architecture, a working prototype of the user interface, and a costed delivery plan. It is not yet deployed with a customer.

  1. Next

    Phase 1: proof pilot

    One team, one project, read-only: sourced answers, monitoring and a morning brief.

  2. Phase 2: agile pilot

    Adds scope forecasting, dependency analysis and documentation checks. Still no writes.

  3. Phase 3: full version

    Writes with an approval queue, programme level, and backup checks.

07 Fit

Who we are building it for

Fintech and banking
Data residency and supervisory obligations.
Healthcare
Project data adjacent to patient records.
Public sector
National data sovereignty requirements in procurement.

The console assumes your projects live in a project management tool and that items are kept up to date. Without that, there is nothing to watch.

We are looking for our first design partner

If you run projects in a regulated environment and want to see how the console would work for you, get in touch. A design partner shapes what we build and gets preferential terms.

Get in touch

For investors

We are building the console as a product with its own hardware appliance, for a market that has no alternative today. We are happy to share detailed materials.

Contact us

Frequently asked questions

Is the console available yet?

No. The console is in development and is not yet deployed with any customer. We are looking for our first design partner.

What systems does it connect to?

In version 1, OpenProject and XWiki, through their official interfaces. Further systems will follow demand.

Does our data leave our network?

No. The language model, retrieval and index all run on an appliance inside your own network.

Will the console replace the project manager?

No. The console gathers and evaluates state. Decisions about scope, dates and people stay with a human.

Why an appliance rather than the cloud?

Because our customers are not allowed to send project data to a cloud. Sovereignty is not an add-on; it is the reason the product exists.