Pocketbase Hosting

1. Open the pod logs in PikaPods and find the secret signup link. Treat it as a credential and do not share it.
2. Use that link to create the first superuser account. The administration dashboard is at your pod URL followed by /_/.
3. Create collections and review their API rules, then connect your frontend to the pod URL using an SDK or the Web APIs.

The getting-started documentation explains the dashboard and API. Collection rules are locked to superusers by default; configure the intended access rather than making everything public. Never put superuser credentials or tokens in a public frontend.

No. PikaPods sets up and runs Pocketbase for you, including OS and app updates and HTTPS. You won't touch Docker or a server. Your files and database stay accessible if you ever want to move them elsewhere.

Yes, as the backend for an app you build. The official JavaScript SDK supports browsers, Node.js and React Native, while the Dart SDK supports web, mobile, desktop and command-line applications. These are developer libraries, not ready-made consumer apps. Point the SDK at your pod URL and follow the client integration guide.

For verification emails, password resets and email-code sign-in, configure your own SMTP service in Dashboard > Settings > Mail settings; the mail provider may charge separately. OAuth2 sign-in needs an application registered with the chosen provider and its client ID, secret and redirect URL. Neither is necessary just to start with database records and password sign-in. See mail configuration and authentication.

Set up incremental backups to S3 in your pod settings for automatic nightly snapshots, or download your files and database yourself. We keep whole-server backups for server failures, but they aren't a per-pod restore service, so your own backup is what protects your data.

You can use Pocketbase instead of Firebase and AWS Amplify. PikaPods runs it for you, and you can move your files and database elsewhere.

Both give an app a database, authentication, file storage and realtime updates. Firebase is a managed Google platform that scales on its own infrastructure. PocketBase is one app with a SQLite database running on your pod, which keeps things simple but limits you to what that pod can handle. It's not compatible with Firebase's APIs, so moving an app means changing its backend code.

Upstream does not recommend PocketBase for production-critical applications before version 1.0 unless you accept compatibility changes and occasional manual migrations. Assess that trade-off before choosing it for a critical system; see the upstream warning.

No. Its API access rules control access, but superusers can access all records and bypass those rules. The optional settings-encryption feature covers application settings such as mail and storage credentials, not end-to-end encryption of your app’s records. See API rules and settings encryption.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

You do. And you're in full control. If you ever want to download, migrate, edit or delete your data, just enable file and database access for your pod and it will be right there.