Your people are already building their own software. Give them somewhere it's safe.

With Core, anyone can get the tool they want just by asking, built on the company's real data. It comes with apps that are good to work in from the first morning, and no app can keep a copy of the data or send it anywhere.

Open the demo workspace Read the docs

No account to create: walk around Halden Studio, a six-person design studio, as anyone on the team. The demo is private, so ask whoever sent you here for the passcode. Or host your own.

Core · just now Sam asked for a list of who still owes us. Built on the same records as everyone else.

Two people, one copy

Maya ticks. Sam reshapes. Core writes it down.

Animation: the same seven task records shown by two apps side by side, Maya's Tasks board and Sam's own checklist version of Tasks. Maya ticks a task on her board and it disappears from Sam's list at the same moment, because there is one copy. Sam then asks Core to group his list by client with open invoices beside each; only his app changes. Finally Core moves a deadline for him; both apps update, and every change appears in the shared log with who made it and from where.

Already happening

Personal software is here. So are the shadow copies.

People are right to build their own tools: the AI they use at home is often better than the software they get at work. The trouble is where the data ends up. To make a tool useful, they paste customer data into Claude, Cursor or Lovable, and the tool keeps it somewhere convenient and starts making decisions on it. A month later there are five versions of the pipeline, a customer list in someone's browser, and nobody can say which number went into the board deck.

“What's in the open pipeline?”

pipeline-export.xlsxexported 12 days ago€412,000
deals-dashboardits own copy · synced nightly€389,500
forecast-botsaved export · unknown age€451,200
Board deck, slide 4pasted by hand€398,000
Corelive · the only copy€351,500
  • Drift. Every copy starts going stale the moment it's made. Five tools give five answers, and the meeting is about which one is right.
  • Leaks. Customer data ends up in tools nobody reviewed, behind keys nobody rotates, in places nobody remembers when someone leaves.
  • No trail. When an auditor, a data subject or the AI Act asks where the data went and who changed it, nobody can say.
  • Bans don't hold. Block the tools and the work moves to personal accounts. And the board still wants to see AI being used.

For the people who use it

Good to work in from day one. Yours the moment you ask.

Core comes with apps that do the job from the first morning, and most people use them as they are. When you'd like one to work your way, say so in a sentence: it changes for you alone, on the same live records as everyone else, and nobody has to shut it down.

Built-in appsMail · Calendar · Tasks · Docs · Files · Clients · Projects · Invoices · Data

One source of truth

Every version reads and writes the same records. Every change says who made it, from which app, and can be undone.

1copy of the data6people, 8 own versions0apps that can send it anywhere
Tasksas it comesBuilt-in

Everyone's work in three columns, ready on day one. Sam is in finance: he doesn't need a board, he needs to know what's late.

Sam asks: “Just my tasks, by deadline, overdue on top.”

Same 70 records
Sam's Tasksa minute laterYours v1

His own tasks, by deadline. Same records, live: Maya ticks one off on her board and it's gone from his list.

In the demo, five of the six have changed an app or two to suit them and use the rest as it comes. Ruben hasn't changed a thing.

  • MMaya

    Maya's Calendar opens on her meeting load per day, the free focus blocks in between, and one click to protect them.

  • SSam

    Sam's Invoices put receivables aging first, a cash-in forecast by week, and one-click chase tasks for each client's account owner.

  • PPriya

    Priya's Clients open on the pipeline, with deals that have gone quiet for five days. Her Mail is grouped by client, biggest live deal first.

  • LLotte

    Lotte's Docs are a writing room: typewriter scrolling, an outline of your headings, and a distraction-free mode.

  • DDaan

    Daan's Files are built for someone who lives in folders: side-by-side columns and everything on the keyboard.

  • RRuben

    Uses every app as it comes. That's fine too.

Yours→Team→Built-in You see your own version if you've made one, otherwise the team's, otherwise the one Core comes with. An admin can share a good version with the whole team. Every version is kept.

For the people who sign off

Say yes to every tool your team wants to build. Keep one source of truth.

The freedom your people want is exactly what you're worried about. Core makes yes the safe answer: they get the tools they ask for, and you decide in one place who sees and changes what, with one record of every change, held in place by how Core is built rather than by a policy anyone has to remember.

One place to audit

Every record and every change: who made it, from which app and version or through the agent, before and after. Undo from the log.

Spot the good ones

An admin can open any version someone has made, check it, and share the good ones with the whole team.

Nothing to chase when someone leaves

Personal apps hold no data. Their owner's tools go; the records stay exactly where they were.

Nothing new to look after

A personal app brings nothing of its own to run, sign in to or store. There's nothing behind it to patch, back up or forget about.

AI use you can point to

The agent works as the signed-in person: it sees only what they may see, and every change it makes is marked “Core agent” in the log.

Runs where you choose

Host it yourself, next to the rest of your systems. The only outside service that sees your data is the AI model the agent talks to.

What you've probably looked at

Sensible options, every one. None of them let everyone build on one copy.

  • Ban it by policy

    Good atA clear rule, written in an afternoon.

    Falls shortPeople build anyway, on personal accounts, where you can't see the data at all.

  • Low-code platforms

    Retool, Power Apps, Airtable

    Good atGoverned apps on real data, with IT in control.

    Falls shortA few people build for everyone. The queue gets shorter, not gone, and nobody gets a tool shaped to how they work.

  • Enterprise chat assistants

    ChatGPT, Copilot, Claude Enterprise

    Good atAI for everyone, with admin controls and data agreements.

    Falls shortWhat they build lives in a chat, beside your systems rather than on them. Results leave as pasted tables and spreadsheets: new copies.

  • Warehouse and BI

    A warehouse plus dashboards

    Good atOne trusted place for reporting.

    Falls shortRead-only for most people. The day-to-day work still happens in other tools, and that's where the copies are made.

  • Vibe-coding platforms

    Lovable, Bolt, Replit

    Good atAnyone can build a real app in an afternoon.

    Falls shortEvery app keeps its own data, so every app is another copy of the data and another thing to secure.

  • Core

    DoesAnyone gets the tool they want, by asking, on the company's data.

    BecauseApps can't keep or send data. One copy is how it's built, not a rule people follow.

    Asks of youThe shared records live in Core.

How it works

Three layers, one rule.

The ruleApps never keep data. They work on the shared records, and can't send anything anywhere else.

The agent

Where you ask.

Questions about the work, updates to records, changes to your apps: in plain words, acting as you.

Your apps

Everyday apps, each one yours to change.

Apps for clients, projects, tasks, invoices, docs and more, all on the same records. Anyone can have their own version of any of them, or ask for a new one, and only their screen changes.

The shared records

One source of truth. The only place data lives.

Every client, deal, task and invoice lives here once, shared by everyone. Each change is checked against the person's role, recorded with who made it and what it was before, and can be undone.

The agent

Ask, and it's done. As you, on the record.

The agent sits on Home and beside every app. It knows which app you have open and what you're looking at, so “change this” means this.

01Ask about anything

Which invoices are overdue?

✓Queried 32 invoices

Three, €24,650 in total. Kunsthal Noord's HAL-2026-017 (€12,400) is the oldest, 22 days late; Fietsfabriek owes €11,600 and De Groene Hal €650.

Draft the remindersNot now

Answers come from the live records, as you see them. No exports, no stale copy.

02Change any app, just for you

Put overdue invoices on top and show how many days late they are.

✓Edited Invoices

Changed Invoices for youYours v2 Overdue first, with a days-late column. OpenUndo

The change becomes your version of the app. Colleagues keep theirs; undo is one click.

03Bring up any part of any app

Show me Daan's open tasks.

Open tasks · DaanOpen in Tasks ↗ Fix fare rounding on return trips2 days ago Price rules: frame, battery and accessoriesWed 3D preview performance on low-end AndroidThu

A board, a card or a chart from any app appears right in the conversation, live, and you can work in it there.

Guarantees

Apps can't keep or send data. Not won't: can't.

Nowhere to keep it, no way to send it

An app can't save anything and can't reach the internet. All it can do is ask Core for records, as the person using it, and Core decides.

Keep datanever Send datanever Read recordsas you Change recordsas you, logged

Every change is attributed, logged and undoable

Who made it, from which app and which version, or the agent, with the full record before and after. An app can't claim to be something it isn't: Core records that itself.

14:02S Sam Okafor Core agent
Send the milestone 2 invoice · due Sun → Mon 2 Nov Undo

Permissions live in one place

Whoever runs IT decides, per kind of record, which roles can see it and which can change it. Core checks it every time anyone looks at or changes a record, whichever app or version asks, or the agent. Change a rule once and it holds everywhere, straight away.

See invoicesfinance See dealssales, finance Change dealssales Tasks, docseveryone

The shape of the data is decided centrally

Apps can't invent fields. An app that tries to save one that doesn't exist is told no, in a sentence. Need a new field? An admin adds it by asking Core, and every app sees it right away.

What the app is told: “estimate” is not a field of Task.

Questions

Isn't this just another low-code tool?

Low-code tools give a few builders a canvas and their own place to keep data. Core starts from one shared source of truth and a full set of apps everyone can use straight away, and lets each person change theirs by asking. Apps can change as often as people like; the data stays put.

Does everyone have to build their own apps?

No. The apps Core comes with are complete, and most people use them as they are. Making one your own is there for when you want it, by describing what you'd like in a sentence. Nobody needs to be technical or creative to get value on day one.

Is it ready to roll out?

Not yet. It's a working demo: one workspace, sign-in with a shared demo passcode, no single sign-on. What you can try today is the part that matters: the shared records, apps that can't keep data, everyone's own versions and the agent, all working for real. You can also host it yourself.

Can an app see data I can't?

No: an app runs with exactly the permissions of the person using it. Whoever runs IT decides, per kind of record, which roles can see it and which can change it, from inside Core. A change applies everywhere at once: in every app, including the ones people build, and in what Core's agent can read. Every change to it is in the log. Not there yet: rules for single records or single fields, and roles beyond the four Core comes with (admin, finance, sales, member).

Do we have to move our data into Core?

Today, yes. Core's apps and agent work on the records that live in Core. Your other systems can be wired to read and change those records, under the same permissions and the same log, but there are no ready-made connectors yet.

What if the agent breaks my app?

Every change is a new version of your copy. Undo goes back one, the Versions menu goes back to any of them, and “Back to the team version” switches you back without deleting yours. The data never lived in the app, so nothing is lost.

Where does the agent run, and where does data go?

Inside Core, as you. It reads and changes records the same way the apps do, under your role, and its changes are marked “Core agent” in the log and undo like any other. The model is Claude, from Anthropic, so what the agent reads in a conversation is sent there. Apps never send anything anywhere.

Do we have to stop people using ChatGPT or Claude?

No. Core doesn't replace the assistants people already use. It gives the tools that work on company data a place to live, so they stop becoming copies.

Change something. Then look at it as Sam.

The demo is Halden Studio: six people, 14 clients, 70 tasks and two weeks of who-changed-what. Pick anyone on the team, ask Core to change an app, and switch to a colleague to see that only yours changed. Then open the log and find every change, with who made it and from where.

Open the demo workspace