Where are we with Northstar?
The website is delivered. The £8,400 invoice is overdue, and the client expects to pay Friday.
Retrieved with
One business.
One Twin.
Any AI.
Your Twin connects the records spread across your systems. Ask who owes what, prepare the weekly review and check the sources behind each answer.
Your Twin · From records to useful work
Connect the systems you useKeep your original records in the systems you use
Accounting · payments
Xero
SunSystems
Stripe
GoCardless
XeroSunSystemsStripeGoCardlessDocuments · files
Microsoft 365
SharePoint
Google Drive
Microsoft 365SharePointGoogle DriveKnowledge · CRM
Google Docs
Google Sheets
Notion
HubSpot
Google DocsGoogle SheetsNotionHubSpotEmail · calendar
Gmail
Calendar
Outlook
GmailCalendarOutlookChat · meetings
Slack
Teams
Granola
SlackTeamsGranolaEngineering · data
GitHub
Linear
GitHubLinearPostgres
MySQL
SQL Server
Other connections agreed for your first workflow
Mercury Labs has delivered for
Client work by Mercury Labs, the team behind your Twin.
Spend less time assembling the picture.
Your Twin connects the pieces across the systems you already use.
01Scattered sources
Understanding the work should not mean chasing updates and rebuilding spreadsheets.
02Follow Northstar
Northstar’s invoice, project and latest conversation belong to the same relationship. Follow them together.
03A shared understanding
Your Twin links the same customer across systems and connects their invoices, projects and commitments. The sources stay available to inspect.
Twin chatShared context One Twin. Your tools. The same business knowledge.Example interfaces · External tools connect with your permission
04A useful answer
Ask the same question in Twin chat, ChatGPT, Claude, Gemini or Copilot, or from your own code through the CLI, SDK and API. Each uses the same connected records and definitions from your Twin. In Microsoft 365 Copilot and Teams, your Twin appears as an agent your team can ask.
ChatGPT
Claude
GeminiYour Twin finds the match. You make the call.
When records in two systems look like the same customer, your Twin brings the match to your Inbox with the evidence side by side. Accept it, decline it or leave it for later. An accepted match can be undone.
An illustration of a proposal in the Inbox. Xero's contact Tarnwick University and HubSpot's company University of Tarnwick look like the same customer: their names are 84% alike and their website domains are identical, at 90% confidence. A person accepts the match, and the two records become one linked customer.
Agree the meaning. Reuse the understanding.
Which records describe the same customer? What counts as overdue? Your Twin connects identities, relationships and definitions, then checks the calculations against your data.
Sample workspace
Define it once. Ask it anywhere.
Ask three people what is overdue and you may get three numbers. Your Twin agrees each definition with you once, then uses it for checked answers wherever your team asks.
An illustration of a definition proposed in the Inbox. From the amount due, due date and status of Xero invoice INV-0027, your Twin proposes what counts as an overdue invoice: money is still owed, the due date has passed, and the invoice is not voided or deleted. On this workspace's data that is 7 of 16 open invoices. A person accepts it. The same thing is then asked in Twin chat and in ChatGPT, in different words, and both answers give £9,223.08 and name the definition and version they used.
01Drafted from your data
Your Twin reads the systems you connect and drafts each definition in plain terms: what it counts, and what it leaves out.
02Accepted by you
Each definition comes to your Inbox. Your Twin uses it for checked answers only once an admin has accepted it.
03Named in checked answers
A checked answer shows the definition and version it used. A change is a new version, back in your Inbox for review.
An answer you can check.
See who owes what, using the same definition of outstanding debt. Inspect the invoices, ageing calculation and sources behind the answer.
the sources are
right here
Sample workspace
Your Twin. Your infrastructure.
A dedicated server for your business on Core, Scale and Enterprise, with control over where it runs. Team runs on a shared deployment.
European Union
Available today
United States
Available today
United Kingdom
In development
The region is where your server runs. Model processing can take place elsewhere, depending on the provider you use.
- Dedicated server
- On Core, Scale and Enterprise, your Twin runs on a server dedicated to your organisation.
- Read-only connections
- It reads the systems you connect without changing the original records.
- Your model provider
- Requests go to the AI provider configured for your organisation.
- Audit trail
- Checked answers show the definition, version and sources they used.
Cyber security certifications
Mercury Labs, the company behind MLX, holds both certifications through its legal entity, Mercury Digital Assets Limited. Scope: whole organisation.
Mercury Labs is a Crown Commercial Service supplier.
Why keep AI in the UK
Your question never leaves the UK.
For many firms the hard question about AI isn’t what it can do. It’s where the data goes. A fully UK-hosted Twin keeps the whole path, from the question to the answer, inside the UK.
- 01Say yes to sensitive workClient files, contracts and personal data stay inside the line your policies draw, so AI can reach the work it was kept away from.
- 02No outside model providerPrompts and business context go to a private model on UK GPUs, not to a third-party AI service.
- 03One boundary to reviewServer, storage, model, logs and backups sit in one place, so your security review has one set of answers.
- 04The same checked answersSources, definitions and checks work as they do today, whatever model answers.
Runs on Project Venus, our private model: a draft model that predicts tokens ahead for speed, an adapter trained on real tasks, and no metering on token usage, subject to concurrency thresholds. Read the research
United KingdomIn development
ServerUK datacentre
StorageUK datacentre
Private modelUK GPUs
Logs and backupsIn the UK
Outside AI provider
Not on the route
Your choice of model
Or use the models you already know.
Your Twin can answer through Venus, our private model, or through OpenAI, Anthropic or Google. Whichever you choose, it works from the same records and definitions, and each checked answer shows its sources.
Requests go to the model configured for your organisation.
Sample workspace
Forward-deployed engineering
Our engineers work alongside your team.
Reserve engineering time to connect your systems, check a first workflow or extend your Twin. We agree the work with you.
- 01Work with our engineersWork directly with engineers on your systems, business questions and the results you need.
- 02Faster path to live useConnect the systems for a useful workflow and check the results with your team.
- 03Expand where it helpsAgree additional connections and workflow improvements as your needs change.
£1,200 a day. Larger or dedicated teams are agreed separately. Add engineering days
Sample workspace
We connect the systems. You help define the result.
Start with one important workflow. In two focused weeks, we connect its systems and check the results with your team.
Days 1–5
Connect priority systems
We agree the question, connect the systems it needs and start with read-only access.
Days 6–10
Build and check your Twin
Your Twin connects the records, defines the calculations and tests them against your data. Work that fails the checks is left out.
End of week 2
Review the Twin, then switch it on
Check the result against real business examples with your team. The release stays off until you switch it on.
Get started today on Team, from £75 a user a month on a shared deployment. Core from £2,000 a month with a dedicated, managed deployment and AI usage from £250 a month. Optional engineering at £1,200 a day. See pricing
The questions we hear first.
Keep your existing systems. We agree a first workflow and connect the systems it needs, starting with read-only access.
Mercury Labs engineers work with your team to connect the relevant records, agree business definitions and test the calculations against your data. You review the result before switching it on.
Your first workflow
Start with the question your team keeps chasing.
Show us a recurring report, an awkward handover or a decision that takes too long to prepare. We agree a first workflow with you, then connect its systems and check the results with your team in two focused weeks.