Skip to content
Docs Take your app away to run on your own

Take your app away to run on your own

Download your whole app with its data as a program for Linux, macOS or Windows, or as a Docker image, and run it on your own computer or server.

Who can take an app away

You can download your whole app, with its data, as a program that runs on a computer or a server of your own, without Base Captain. Only an owner of the base can do it, and only when Base Captain has turned this on for that owner. Ask us at Contact. Other users, admins included, do not see Export the app.

Export the app

  1. In your base, open Settings, then Export the app.
  2. Choose the system: Linux, macOS, Windows or Docker.
  3. Click Export for Linux (the button names the system you chose). The export runs in the background: you can leave the page. It also shows in Activity, Background jobs.
  4. When it is ready, we send you an email, and the page shows the zip with Download and the day it is removed. We keep each download for seven days.

One export of a base runs at a time. Every user of the base gets a notice when private conversations leave with an export.

What the zip holds

Each zip has one folder, named after your base, with:

  • the program, built for the system you chose, with the pages of Base Captain in it;
  • data/, the data of the base when you exported it: the tables and the code of your app, its items, files, comments, history, users, channels and their messages, the Files page and the shared mail, and your secrets;
  • README.txt, the steps for that system;
  • LICENCE.txt, the licence of the program, and NOTICES.txt, the open-source parts that the program includes, with their licences.

The Docker zip holds an image file for docker load in place of the program and data/, a compose.yaml that also runs the database, and env.example, the settings to fill in. No zip holds source code.

The program says whose copy it is: --version prints the app, the Base Captain user who exported it and the time of the export.

Run it on Linux, macOS, Windows or Docker

Each README gives the steps for its system: install PostgreSQL 16 or newer, run setup, which makes the database and loads the data, then serve. You set the owner's password at setup. No other password leaves Base Captain: the other users get an email to set theirs when the program first starts.

  • Linux (x86-64): it starts with the machine as a systemd service.
  • macOS (Apple silicon): Postgres from Homebrew, and a launchd job that starts it with the Mac.
  • Windows (x64): the Postgres installer, and a scheduled task that starts it with Windows.
  • Docker: docker load, then docker compose up. On its first start it sets the base up from the settings in .env; the database and the files are kept in Docker volumes.

Each README also says how to put the base behind HTTPS and how to back it up and restore it with pg_dump and the files folder. We have not yet followed the macOS and Windows steps on a Mac or a Windows PC ourselves: if a step does not work for you, tell us.

What stays behind

The program runs your app: its lists, items, files, chats, automations, schedules, workflows, forms and payments. These stay behind:

  • the assistant, agents and machines, and the MCP server: a workflow step that an agent did waits for a person;
  • changing the app: tables, views, roles, forms, print templates, automations and workflows cannot be edited;
  • mail in, sign-in with Google or Microsoft, and two-factor authentication.

Nothing updates by itself. After a change in Base Captain, export again. Your base in Base Captain goes on as before: the export changes nothing in it.

The licence, in short

The program is licensed to your business. In short:

  • you may run it, back it up and restore it, for your own business;
  • you may not give, sell or share it with others, or run it as a service for others;
  • you may not reverse engineer it, except as far as the law allows;
  • no updates and no support beyond your plan;
  • the data is yours, and the program sends nothing to us.

LICENCE.txt in the zip is the whole text. The open-source parts stay under their own licences.

Keep the export safe

The export holds your base's secrets, such as its keys to payment and mail services, and the config file that setup writes holds them too. Keep the zip and the folder where only you can read them, and do not push the Docker image to a public registry.

Loading