Your team's ideas. Your actual software.
Connect an existing project or start something new. Croft works with the software your business runs, so the improvements go where they matter.
Your software.
In your hands.
The people who know what needs to change can finally change it.
INSIDE CROFTMeet Rowan, our fictional cabin business
A conversation. A working product. Real Croft. Fictional business. A closer look at how work becomes software.
In good company. Teams building with Croft.
Musterworks
AutoComms
polarQAPACITI
From “could we?” to “it's live.”
You know the business.
Now help shape the software.
The booking rule that needs changing. The report everyone asks for. The idea that never makes it to the top of the queue. Give it to Orra, and work through it together.
The workspace
A conversation that changes things.
Tell Orra what you need. Watch it take shape in a live copy of your app. Click around, check the details and ask for the next improvement.
Chat and the running product, side by side.
Captured in Croft · Rowan demo projectPrototype mode
See it before you build it.
Switch to Prototype and ask for a welcome card, a quicker drawer, a calmer dashboard. Orra returns a round of takes side by side, styled from your own app, with nothing changed underneath. Pick one, ask for another round, or build the one that feels right.
Three takes. Nothing in the app has changed.
Captured in Croft · Rowan demo projectRecorded decisions
Get the important decisions right.
Agree the details that matter, then keep the answer with the work. Here, Rowan's confirmed arrival policy has unlocked the cabin instructions that were waiting on it, and the next ticket after that.
A confirmed policy. The next work unlocked.
Captured in Croft · Rowan demo projectThe plan
Know what comes next. And why.
See the work in dependency order. The plan follows what has actually shipped, so your team spends less time moving cards and more time moving forward.
Real dependencies. A clear next step.
Captured in Croft · Rowan demo projectLive preview
Use it before you approve it.
Open a booking. Try a filter. Check the reminder. Review the real experience your customers and teammates will use, then decide whether it is ready.
A working app you can actually try.
Captured in Croft · Rowan demo projectThe Glen
Your project has a home.
The Glen gives your project a landscape of its own. Return to your work, see what is happening and pick up the conversation where you left it. Step away and the workspace sleeps; come back and it wakes with everything intact.
A place to return to, as your product grows.
Captured in Croft · Rowan demo projectThere's a whole workshop in here
Go beyond the chat.
Get your hands on it.
The preview is just the beginning. Your projects, data and running services are all within reach.
A window into your database
The records behind the experience.
Open your database inside Croft. Browse tables, inspect a record, filter the rows or write a query. Here are Rowan's fictional bookings, in the real data browser.
SQL, when you need it
Go straight to the answer.
Use the query editor to explore the data behind a question. Check a result, inspect the rows and bring what you learn back to the work.
From an idea to a project
Give the next thing a beginning.
Describe what you want to exist, give it a name and choose where it lives. Croft creates a real project your team can keep building and your own repository to take with you.
The environment, in view
Your app has a whole workshop.
See the apps and services your project runs on. Manage its database and inspect the setup from the same place you build, with the detail there when you need it.
Captured in the real Croft app. Rowan and its records are fictional.
A little light. A lot of context.
Meet your newest
collaborator.
Orra gets to know your software and the people building it. She asks the useful questions, makes the changes and checks her work in a real browser.
The decisions and discoveries stay with the project. Pick up tomorrow without starting from scratch. And when you are not sure where something lives in Croft, tap her and ask.
Meet Orra in a demoORRA Your project's memory, too.
“Can we remind guests before they arrive?”
Let's work out the details first.
01
How far ahead should the reminder go?
02
What should a guest know before arriving?
03
What happens if the booking changes?
An illustrative conversation for Rowan
Ask Orra anywhere
Lost? Tap her.
She knows the way.
Orra is on every page of Croft. Tap her and ask about the product, your setup or where something lives, and she answers in a sentence and offers the door.
Ask, and she takes you there.
Where do env variables live? How do I invite a teammate? What is a workspace? A short answer, then a door card to the exact page, tab or setting. You click it. She never navigates for you.
She can do it, too.
Ask her to turn on nightly backups or add a domain and she offers the change as a card with the confirm sentence written beside it. Anything secret, you type yourself.
Always current.
Every door she offers is generated from the product itself, so her answers cannot drift from the build. New teammates get walked in the same way, one door at a time.
ASKED FROM THE GLEN
Built for the whole team
Software everyone
can get their hands on.
Croft is a place a team works, not a tool for one person. The people who run operations, support or finance build what they need. Everyone tries it in the same running app, on every screen it will be used on.
Every screen
Phone, tablet and desktop, side by side.
Open the same page at several sizes at once. Each frame is a live copy of the real app, so a change shows everywhere the moment it lands. Pick a preset or drag an edge for a size of your own.
Together, in the app
Talk about it where it lives.
See who is here. Talk it through in the team chat beside the preview and mention a teammate. Send a stakeholder a link to the running app, without handing over the workspace or the code.
Internal tools, without waiting for a dev team.
The booking desk, the month-end report, the handover checklist. The team that needs the tool describes it, tries it and keeps improving it, while engineering keeps review and permissions.
How teams own their softwareEngineers keep their own tools.
Connect Claude Code, Cursor or any MCP client to Croft with an agent key. A key acts as the person who made it and can never do more than they could.
Go back to any point.
Roll back to an earlier prompt, or edit one and run again from there. Every step Orra took is there to read, so the team can see how the software got here.
Pick up where you left off.
Step away and your workspace sleeps. Come back and it wakes with every chat and change intact, and whatever a teammate saved in the meantime is pulled in for you.
Captured in the real Croft app. Rowan and its people are fictional.
Confidence, built in
More people building.
Still your call.
Give your team room to improve things, with clear boundaries around the software your business depends on.
Try the change before it goes live.
Click through the running app, check the details and bring a teammate in. Reviewing a change should feel like using your product.
People keep the final say.
Choose who can change what. Work outside those permissions goes for review, and sensitive actions pause for approval.
A home for production, too
Build it here.
Give it a place to live.
Hosting is part of Croft. Set up production, choose from the available regions and give your app an address your customers can use.
Choose where production runs
Place the production app and its dedicated Croft-managed databases in your selected region.
Give live data its own space
Choose a separate production database, so the team can keep building against development data. Turn on nightly backups and restore from the same tab.
Make it yours
Start with a Croft address, then connect your own domain, one per app if you like. Review releases, read the logs and look at production with Orra from the same place.
FROM WORKSPACE TO PRODUCTION
Built here. Hosted in the UK.
UKMusterworks runs in Croft’s UK deployment.
Planning around data residency?
Tell us what needs to live where. We'll walk through production hosting, development and the services involved.
Once it's live
Know who came.
Nothing to install.
Every production app on Croft has its own traffic view. Who visited, where they came from, what they looked at and how long they stayed, counted without cookies.
It opens with a sentence about what changed, not a wall of numbers. A slow page or a broken link is called out, and you can look at it with Orra.
WHO IS USING IT, AND WHAT THEY HIT
Can we use Croft with our existing software?
Yes. Connect your GitHub project and Croft works out how to run it, including its dependencies and backing services. You can also start a new project in Croft. Bring your software to a demo and we can walk through what it needs.
Does everyone on the team need to be technical?
No. Describe what you need in plain language, work through the decisions with Orra, then try the result in a live preview. Engineers can inspect the code and set permissions; the rest of the team can focus on how the software should work.
What stops an unwanted change reaching production?
Permissions determine who can change each part of a project. Work outside a person's scope goes to a reviewer. Sensitive operations require explicit approval. When Croft runs a whole plan, the final merge is still a human decision.
Can the whole team work in it, and on their phones?
Yes. Teammates share the same running app, see who is active, and talk it through in a team chat beside the preview. The preview shows a page at phone, tablet and desktop sizes side by side, so every screen gets checked before a change goes live.
How do we learn our way around?
Ask Orra. She is on every page. Tap her and ask where something lives or how to set it up, and she answers in a sentence and offers a door card that opens the exact page, tab or setting. She can make small changes for you too, with a confirm step. New teammates get walked in the same way.
What does it cost?
Croft is free to start. Paid plans are per seat, hosting is priced per app by size, and there is no metered compute to watch. The pricing page has the details.
Who owns the code?
You do. Your project lives in a GitHub repository. You can clone it, move it or keep developing it with your own tools and team.
What will we see in a demo?
A walkthrough of deciding, planning, building and reviewing a change in Croft. Bring a real request your team has been waiting on. We will talk through your existing software, who needs access and how Croft could fit your team.
Make room for what's next
That idea you've
been sitting on?
Let's make it real.
Bring one thing your team wishes the software could do.
We'll show you a different way to get there.