clundra

Internal tools · Small products · Prototypes that stuck

Build software.
Share it like a document.

Clundra turns your code into an app with its own link, built-in access and a history you can go back to — ready to send to someone.

Git repository · Container image · Postgres

See how sharing works
  • One app, one link.
  • Access you control.
  • No login code needed.
  • Rewind any change.
customer-portalcustomer-portal.clundra.com
LiveShare
History
Published  Live2 min ago
Moment saved8 min ago
Share “customer-portal”
Who can open it?
Only meNobody else can open it.
Workspace membersEveryone in this workspace.
Anyone with the linkNo sign-in required.
NicuOwner
FinanceViewer
AnaEditor
Copy app link

Shareable by default

Share an app
like a document.

Anyone you send it to can open it in a browser. No account, no install, nothing to run.

Keep it to yourself, open it to your workspace, or let anyone with the link in — and change your mind later without redeploying.

Clundra checks people at the edge, before traffic ever reaches the app. So an app with no login code of its own can still be shared with exactly three colleagues, and un-shared just as fast.

Software should be as easy to send as a document.

The app’s own page

One app.
One page.

Open an app and the first thing it tells you is what people see when they open the link. Its address, who can open it, its settings and everything that has ever happened to it are all on that one page.

You never have to reconstruct the state of your app from six places that each know part of it.

customer-portalLive
nowWhat people see when they open the link
customer-portal.clundra.comsince 2h
Workspace members can open it
History
PublishedMon
Moment savedTue
RewoundToday

From code to a link

Paste a repo.
Get a link you can send.

Clundra reads the repository and works out what it’s made with, how it builds and what port it starts on. Tick a box for a Postgres database. Nothing is live until you press Publish.

  • No cloud account to set up first
  • No DNS, no certificates
  • Nothing is live until you publish
  • Change the setup later, in place
Publish an app
One field. We work out the rest.
Repository
github.com/acme/customer-portal
Made withNext.jsdetected
Starts on port3000detected
Builds withnpm run builddetected
DatabasePostgres · 1 GB
Publish →
Environment variables
API_URL = /api
NODE_ENV = production
Deployment
Auto deployON
Branchmain
Build
npm run build
npm start
Domains
app.acme.com
customer-portal.clundra.com
Health check
/health
Port & exposure
3000 · Public

Click the row — the settings open in place

Built-in way back

Every change
has a way back.

Every publish is a moment in the app’s history. When a change breaks something, pick the last working moment and put the app back — its code, its settings and its data together.

The rewind is written to the history too, so the app can always account for how it got the way it is.

See recovery in action →
History
10:42v21 published
Healthy
11:08v22 published
Health check pending
11:10Health check failed
The app returned 503
11:11Rewound to v21
Application recovered

Production foundations

Small in audience.
Not in importance.

A tool five people use still needs secure access, data that survives a restart, and a way back when something breaks.

Clundra ships those foundations with every app, so you don’t need a platform team to have them.

  • Isolated runtime
  • HTTPS included
  • Managed secrets
  • Persistent storage
  • App history
  • Recoverable states
Internet
HTTPS + access
Your app
private
PostgreSQL
IsolationSecretsPersistent dataRewind
Internal tools
Dashboards, approval flows, the thing finance asks for every quarter.
Small products
A focused product with a database behind it. Nothing more.
Apps your agent wrote
Code an agent produced for one job, published somewhere real.
Prototypes that stuck
Experiments that now need real data, real access, and to not fall over.

Simple enough to start. Real enough to keep.

Workspace
€20/mo
Includes €20 of usage. Unused credit carries over.
  • Unlimited seats
  • Unlimited apps
  • Custom domains
  • Bandwidth included
  • 7 days of snapshots
  • €5 credit to start, card required
What you run
Hourly
Every line has a monthly ceiling. The cap is the most you can pay.
  • App — €0.01/hr, up to €7/mo
  • Postgres — up to €10/mo, 10 GB
  • 90-day rewind — up to €5/mo per app
  • You never pick an instance size
See full pricing

Prices exclude VAT. Nothing is charged for your first 7 days.

Availability & roadmap

Available now.
Shipping next.

Apps, sharing and rewind are live today. Here’s what you can use right now — and what’s on the way.

Available now
  • Apps from a repo or an imageOne service, built and deployed on its own URL.
  • Managed PostgresConnected and persistent by default.
  • Share like a documentPrivate, invited, workspace, or link.
  • HTTPS + built-in accessAuthentication before traffic reaches the app.
  • Deployment historyEvery change, who made it, what it touched.
  • RewindReturn the whole app to its last working state.
Shipping next
  • Several services per appA frontend and an API as one application, one URL.Q4 2026
  • Fork from a versionBranch a running app from any point in its history.Q4 2026
  • Team access controlsRoles, scoped permissions, shared workspaces.Q4 2026
  • MachinesThe reversible compute primitive, exposed directly.Q1 2027
  • MCP serverAgents operate Clundra natively, inside your permissions.Q1 2027
  • More regionsRun closer to the people using the app.Q2 2027
  • Deeper observabilityMore insight into state, changes and recovery.Q2 2027
NowNext

FAQ

Questions before you deploy?
Here’s what teams ask most.

Yes, for the software this is built for: internal tools, focused products and small services. You get isolation, private networking, HTTPS, managed secrets and persistent data on every app — not just the paid tiers.

The whole application returns to a previous version — every service, its configuration and the connections between them, together. Persistent data tied to that point comes back with it. Nothing to reconfigure, and the rewind itself is recorded in the history.

No. Clundra can authenticate people at the edge, before traffic reaches your app, so a prototype with no auth at all can still be shared safely with three named colleagues.

Not yet. Apps are created and operated from the dashboard today, with scoped access and a recorded history of every deploy. A REST API and a native MCP server are both on the roadmap — the reversibility they need is already built, which is the part that makes handing an app to an agent reasonable.

If it runs from a repository or a container image and talks to Postgres, it will run here. Point Clundra at the source, confirm what we detected, publish.

One, plus a managed Postgres if you tick the box. That covers the software this is built for — a frontend with an API behind it, an internal tool, a small product. Splitting an app across several services is on the roadmap; today, an app is one thing you publish and one link you send.

Apps stop serving traffic, but your data and deployment history stay retrievable for a grace period, and a Postgres dump is one click away for as long as they do.

Build the app.
Send the link.

Start from a GitHub repo or a container image. You get one app, one link, and a way back from every change.

Read the docs