What every OpenCloud app runs on.

The Agent

An AI agent that builds your app from a conversation, then keeps looking after it.

Ask for it like this“Build a holiday planner for the team, with approval from each person's manager.”

• Asks only the questions that matter, then builds, tests and releases the app.
• Starts from what you already have: attach spreadsheets, documents, presentations, PDFs or images.
• Stays with the app. Ask for changes in the same conversation weeks later, and it picks up where it left off.
• Runs on your organisation's own AI accounts: sign in with ChatGPT, or add an OpenAI or Anthropic API key.

Your own coding agent

Prefer your own tools? Codex, Claude Code, ChatGPT and Claude can build on OpenCloud too.

• Connect once. You approve which app it can work on, and your password is never shared with it.
• It follows the same steps as the Agent: build in a private preview, test, then release.
• A command line tool offers the same steps for people who work in a terminal.

Build system

Turns your app's code into a finished release, the same way every time.

• Builds run in a locked-down space of their own, with no access to your passwords, keys or data.
• The only thing a build can reach is the public library of code packages.
• Builds that take too long or use too much are stopped, so one app can't slow down the others.
• The finished build is kept with the version that was tested, so what you approved is exactly what goes live.

Protects you fromA build step quietly reaching your passwords or data.

One description per app

Each app has one short file that lists everything it uses.

• Its server code, background jobs, schedules, web addresses, alerts and the passwords it needs are all listed in one place.
• OpenCloud checks the file before anything goes live, and anyone technical can review it.
• It names the passwords and keys the app needs, but never contains them.

Starters and your brand

New apps start from tested building blocks, styled to look like your company.

• Ready-made screens and components, with accessibility built in.
• Your colours and fonts come through a theme, without OpenCloud's own branding in your apps.
• Working examples to open and try, such as a client portal, a simple CRM and a project board.

Database

A real database for every app, with rules for who can see and change each record.

Ask for it like this“Keep track of our clients, their projects and every invoice.”

• Each app has its own separate space in the database. One app can't read another app's data.
• Rules for who can see each record are always on, for every table, and can't be switched off. Without a rule that allows it, nobody can see a record.
• Changes to how the data is organised are tried on a throwaway copy before every release.
• The app's pages never hold database passwords. Every request runs as the person who is signed in.

Protects you fromThe most common leak in AI-built apps: a table left open to anyone on the internet.

Files

Upload documents, photos and other files without setting up anything extra.

• A file can be private to the person who uploaded it, or shared across the app.
• Each file is saved together with its record, so the app always knows who it belongs to.
• Files can be up to 100 MB each.

Live updates

Changes appear on everyone's screen as they happen, without refreshing.

• Good for shared boards, request queues and dashboards.
• An update only tells a screen that something changed. The screen then loads it with the viewer's own permissions, so nobody sees more than they should.

Email

Apps can send email, and receive it.

Ask for it like this“Send a confirmation when someone books a room, and turn replies into notes.”

• Each app has its own addresses, so replies come back to the right app.
• An incoming email can start server code, for example to log a support request.
• Sending pauses by itself if too many messages bounce or are reported as spam, which protects your reputation.
• Email sent from a preview is captured, never delivered.

Notifications

Send notifications to people's phones and computers, even when the app isn't open.

• People turn them on for each device themselves.
• Notifications sent from a preview are captured, not delivered.
• Every notification sent is kept in a history for 30 days.

Integrations

Connect apps to the tools your company already uses.

• Google Calendar, Drive, Sheets, Docs and Slides; reports from Google Analytics, Search Console and Google Ads; HubSpot; Asana; Slack; Telegram; bank account data through GoCardless; and payments received in Wise.
• You connect an account once. Apps use it without ever seeing its password or keys.
• Every call an app makes through a connection is recorded.
• Previews get realistic made-up data, unless someone switches one connection to live, and that switch is recorded.

Your own integrations

Connect any other system once, and let every app in your organisation use it.

• One app provides the connection, and your other apps use it like a built-in one.
• Passwords and sign-ins for that system are stored once, and only the app that provides the connection can use them.
• It can bring changes in from that system too, such as new orders or updated records.
• Connections stay inside your organisation.

AI features

Add AI to an app: summaries, drafts, details pulled from documents, and images.

Ask for it like this“Read each uploaded receipt and fill in the expense form.”

• They run on your organisation's AI accounts, in the order your admins choose.
• The app's code never sees the passwords or keys for those accounts.
• A request can include files, such as photos or a PDF.

Private previews

A private copy of the app, built fresh for each round of changes.

• It never contains live data or real passwords.
• Open it in your browser. It's clearly marked as not live, with desktop, tablet and mobile sizes.
• Only the exact version that passed its checks can be released.

Made-up people and data

Tests use made-up data and three made-up people, never your real ones.

• An admin, a member and an outsider check that each person sees only what they should.
• Email and notifications are captured instead of sent.
• Integrations return realistic made-up data unless someone switches one to live, and that switch is recorded.

Automatic checks

Every new version is checked before anyone relies on it.

• The app's own tests walk through its important tasks, such as creating and approving a request.
• OpenCloud also looks for errors, broken links, pages that don't fit a phone screen, buttons without labels and tap targets that are too small.

Every release kept

Each release is fixed once it's made, and kept.

• The source code of any release can be downloaded at any time.
• If two people release at the same moment, the second is stopped instead of quietly replacing the first.
• Every release records who made it and when.

Rollback

Go back to an earlier version of the app in one step.

• Rollback brings back the code and screens of the earlier version.
• It doesn't undo changes to the data. Restoring a backup does that.

Backups

Bring an app's data back to an earlier point.

• The database is backed up by itself before every release that changes it.
• You can add daily or weekly backups on top.
• Backups are locked for 30 days, so nobody working on the app, including the Agent, can delete them early.
• Restoring a backup replaces the app's current data with the data in that backup.

Not yetUploaded files aren't included in backups yet.