Skip to main content

PocketBase

PocketBase provides a compact application backend with collections, records, authentication, files, and an administrative interface.

Validation scope

The browser workflow and a stop/start persistence check passed on a disposable installation. Concurrent-write durability, backup recovery, and complete usage accounting remain under review. Do not treat this walkthrough as production storage certification.

Deploy​

  1. Open Services, find PocketBase, and choose Deploy.
  2. Choose a name, environment, and capacity.
  3. Review Preview deploy and confirm the installation.

PocketBase deployment preview

Create Your First Administrator​

The current template does not create an administrator automatically. Opening the public URL with /_/ shows the superuser login screen, not an account that uses your Moltern password.

  1. Open the service's Live Logs after its first startup.
  2. Locate PocketBase's first-superuser setup link. It contains a temporary secret; do not share or screenshot it.
  3. Open that link using your service's public HTTPS hostname, preserving the setup path and fragment. Do not use the listening address printed in the log as a public hostname.
  4. Enter your administrator email and a strong password, confirm the password, and choose Create superuser and login.

If the setup link has expired or no longer appears, do not guess a default password. Ask your workspace administrator for help completing initialization.

Create A Collection And Record​

  1. Choose New collection and give it a name, such as validation_notes.
  2. Add a Plain text field, then create the collection.
  3. Choose New record, enter a short test message, and save it.
  4. Reload the page and confirm that the record is still listed.

A record created in the PocketBase administration interface

The screenshot shows a real saved test record. The collection's API rules are separate from administrator login: review them before allowing an application or an unauthenticated client to read or write records.

Stop, Start, And Delete​

The tested record remained available after Stop service, removal of the runtime, and Start service. Keep backups before changing important data; this single restart check is not a substitute for recovery testing.

When deleting the service, review Delete stored data versus Keep workspace files. Retained files continue to consume storage. Cleanup can take time after the service disappears from the list.

PocketBase documentation