Skip to content
iglo.tech

02 Run · Backend

iglo.base

A database, an API and an admin screen for your app, in one file.

The backend for your app.

Your app needs a database, an API and an admin screen. iglo.base gives you all three in one executable on your own server.

iglo.base is an independently maintained port of PocketBase v0.41.0 to Bun and TypeScript. The REST API, the realtime API, the admin dashboard and the pb_data directory format stay the same, so existing apps, SDKs and data work without changes.

iglo.base removes PocketBase's extension surface: there is no Go framework mode, no JavaScript hooks (pb_hooks) and no dashboard extensions. JavaScript migrations (pb_migrations) keep working. It has no self-update command: update by replacing the executable or the image.

What you get.

  1. 01
    Opens your existing PocketBase pb_data directory as is. PocketBase can still open it afterwards, so you can go back.
  2. 02
    Same REST API, realtime API (Server-Sent Events) and admin dashboard at /_/.
  3. 03
    One compiled executable per platform: linux-x64, linux-arm64 and darwin-arm64.
  4. 04
    A container image at ghcr.io/iglo-tech/iglo.base.
  5. 05
    SQLite only. TLS ends at your reverse proxy: the app serves plain HTTP.
  6. 06
    Not an official PocketBase edition.

Run it.

Download the archive for your platform from the releases page, check it and start the server on your data directory:

shell sh
sha256sum -c SHA256SUMS
unzip iglo-base_<version>_linux_amd64.zip
./iglo-base --version
./iglo-base serve --http 127.0.0.1:8090 --dir /path/to/pb_data

The cutover guide has the full steps from PocketBase, including Docker and the way back.

Documentation.

  1. 01 Overview What iglo.base is and how to move from PocketBase.
  2. 02 Operations guide Install, flags, systemd, Docker, Caddy and nginx, backups, upgrades and the CLI.
  3. 03 Differences from PocketBase What is not there and what you may notice in the API.
  4. 04 Cutover from PocketBase Switch a running PocketBase to iglo.base, and go back.
  5. 05 Releases and the image What a release contains and how the container image is built.
  6. 06 Why iglo.base exists The reasons for the port and what it changes.
—

The rest of the stack

All products →