Backend application # PocketBase backend template with embedded SQLite The marketplace lists a PocketBase container with embedded SQLite, built-in authentication, file storage, and realtime APIs. Provisioning is currently unavailable in the international sandbox. [Get started](https://panel.deplomo.com/signup)[View in marketplace](/marketplace) ## PocketBase template details A single container image with embedded SQLite, an administration interface, and authentication features. Confirm version and resource requirements before deployment. ### Embedded SQLite database PocketBase stores application data in an embedded SQLite database on persistent storage; no separate database service is required. ### Built-in authentication features PocketBase provides email/password authentication and OAuth2 options. Two-factor authentication availability depends on the version and configuration; review the current documentation. ### Realtime APIs Clients can subscribe to record changes through server-sent events (SSE), subject to access rules and application configuration. ### Built-in administration interface Use the admin interface to manage collections and records, configure access rules, and manage users. ### File storage PocketBase supports file uploads and storage. Configure file validation, access rules, and backups for your deployment. ### Compact Go-based application PocketBase is written in Go and distributed as a compact application. Resource use depends on workload and configuration; no fixed request capacity is implied. ## Frequently asked questions about PocketBase Answers to common questions about the PocketBase template, SQLite, and application requirements: What is PocketBase, and when is it useful? How can PocketBase help teams build an application backend? Is SQLite suitable for a production PocketBase deployment? How does PocketBase compare with Firebase or Supabase? How can I add custom business logic to PocketBase? How are PocketBase data and backups handled? ## PocketBase: features and deployment considerations PocketBase is an open-source backend application written in Go. It combines an embedded SQLite database with authentication, file storage, an administration interface, and realtime APIs. Review its current documentation and workload requirements before choosing it for a deployment. ### Embedded database and access rules PocketBase uses SQLite for application data and provides collections, fields, and access rules through its admin interface. Database performance and access control depend on workload and configuration; test your setup and review the current documentation.

Comparison	PocketBase marketplace template	Hosted Firebase services	Other backend platforms, such as Supabase	Build and operate a custom backend
Setup approach	Single-container marketplace template; provisioning unavailable in the sandbox	Setup and billing depend on the provider and selected services	Architecture and resource needs depend on the selected services	Requires application-specific design and implementation
Resource requirements	The catalog template has a 256 MB RAM minimum; actual use depends on workload	Limits and charges depend on provider, plan, and usage	Resource needs depend on the selected service architecture	Resource needs depend on the framework and runtime
Data storage and operating model	The template mounts persistent storage at `/pb_data`; arrange separate backups	Data handling depends on the provider’s service and terms	Self-hosting options vary by product	Self-hosted deployments require ongoing operations and backups
Realtime updates	PocketBase supports server-sent events (SSE) for realtime subscriptions	Realtime features and pricing depend on the selected service	Realtime features depend on the platform and its configuration	A custom implementation may require additional services
Pricing and cost visibility	Fixed monthly EUR packages by zone, subject to hard resource limits	Hosted provider pricing depends on its current plan and terms	Package structure and charges depend on the selected platform	Self-hosting requires infrastructure and ongoing maintenance

### Compare PocketBase with other backend architectures When comparing backend options, consider tools such as [Supabase](/marketplace/apps/supabase) and PocketBase have different architectures and intended use cases. PocketBase runs as a single application with SQLite; developers who need a separate relational database may also consider [Cloud database](/products/databases) or ### Comprehensive authentication and compatibility with popular frontend SDKs One of the biggest advantages of Pocketbase is the availability of official, community-driven SDKs for popular languages and tools such as JavaScript, TypeScript, Dart (Flutter), Python, and React Native. With a few simple lines of code, you can implement registration, login with password, login with social network account (OAuth2) and password recovery in your application without getting involved with the complexities of creating JWT tokens and password hashes. ### Optimum storage and serving of images and files Managing files in applications usually involves a lot of trouble, such as validating file types, resizing images, and protecting private files. PocketBase automates this process with a dedicated file field. After uploading, the images will be automatically cut to the specified size (Thumbnail) and directly accessible through secure web addresses. ### Stability and security on cloud infrastructure Deplomo Running Pocketbase on the Deplomo cloud platform allows you to run your service in an isolated and protected container. Durable NVMe disks ensure the health and survival of your database, and the ability to connect a dedicated domain along with receiving a free SSL certificate makes setting up the backend a pleasant and fast experience. ## PocketBase marketplace template The template defines a PocketBase container with persistent storage. Provisioning is currently unavailable in the international sandbox. [PocketBase template setup](https://panel.deplomo.com/signup)