Self-hosted Supabase stack
Run a self-hosted Supabase stack with PostgreSQL, authentication, REST, Realtime, storage, and Studio using the Deplomo marketplace template. Service creation is currently unavailable in the international sandbox.
Supabase template on Deplomo
The template includes PostgreSQL, row-level security, and configurable backend services. Review the configuration and access controls before use.
Self-hosted Supabase stack
The Deplomo Supabase template includes PostgreSQL, Auth, REST, Realtime, Storage, postgres-meta, and Studio. Public service URLs and settings require review after deployment.
PostgreSQL database
Supabase uses PostgreSQL for its database. Database features and access depend on the deployed version, roles, and configuration.
Authentication services
The template includes Supabase Auth. Email, password, SMS, and OAuth flows require the relevant provider and settings to be configured; SMS and third-party providers may involve external services.
Realtime subscriptions
Supabase Realtime can deliver database change events to subscribed clients. Availability and behavior depend on the deployed configuration and workload.
Frequently asked questions about Supabase
Answers to common questions about Supabase architecture, its services, and connecting applications:
Self-hosted Supabase: backend services on Deplomo
Teams can use a backend platform instead of building every server-side component themselves. Supabase combines PostgreSQL with authentication, APIs, storage, and Realtime services. The Deplomo template runs these components as a self-hosted stack; you manage its configuration and resources.
What is Supabase?
Supabase is an open-source backend platform built around PostgreSQL. Its self-hosted stack includes a database, Studio, authentication, storage, and Realtime services. Review the configuration and access settings before connecting an application.
Supabase uses a relational database based on Postgresql host . For smaller applications, a lightweight backend such as pocketbase may also be worth considering; compare their features and operational requirements.
What should I consider when comparing Supabase with Firebase?
Firebase and Supabase differ in their database models, services, hosting options, and pricing. Compare the features your application needs, where it will run, and the operational work involved before migrating.
Self-hosting Supabase lets you manage its deployment and configuration. Access still depends on your network, hosting provider, and the policies or availability of any third-party services you use.
Compare Supabase hosting options
The table summarizes general differences between the Deplomo self-hosted template, Firebase, and a manual self-hosted deployment. Features, costs, and requirements depend on provider terms and configuration.
| Feature | Supabase template on Deplomo | Firebase | Manual setup on a VPS |
|---|---|---|---|
| Data location and access controls | Data location depends on the selected deployment and configuration | Self-hosted stack; data location and access depend on deployment and network configuration | The provider manages the service; data handling depends on its terms and configuration |
| Database | PostgreSQL | Firestore, a NoSQL document database | Depends on the database you install and maintain |
| Service access and dependencies | Self-hosted services; public URLs and settings require configuration | Access and availability depend on provider terms, network, and project setup | Tracking availability depends on network access and configuration |
| Deployment and setup | Marketplace template with seven components; service creation is currently unavailable in the international sandbox | Configure a Firebase project and its services under the provider’s requirements | Install and configure the required services and container network |
| Pricing and billing | Fixed monthly EUR package pricing | Costs depend on the selected monthly EUR package and its resource limits; no usage-based hourly charges | Provider pricing and limits depend on plan and usage |
Infrastructure and operating costs vary by provider and configuration
The self-hosted template provides a starting point for running Supabase services. Review resource limits, public URLs, access controls, backups, and third-party integrations before deployment.
Supabase deployment guide for Deplomo
- Choose Gitea from the marketplace Service creation is currently unavailable in the international sandbox. When it is available, you can use these general steps to configure the template:
- Select the template: In the console, select the Supabase marketplace template.
- Choose package resources: Review the monthly package limits and confirm the CPU, memory, and storage available for all seven components.
- Connect an application: After deployment, review public service URLs in Variables and configure the URLs required by Studio and Auth. Use the anon key with an SDK or API; the service_role key is privileged and must not be exposed to browser code.
Supabase deployment: summary
The Deplomo template packages Supabase services together, but deployment still requires configuration and ongoing operations. Compare its features, resource requirements, and security controls with your project needs.
Service creation is currently unavailable in the international sandbox.
Run Supabase in seconds
The template includes seven Supabase services. Service creation is currently unavailable in the international sandbox; package limits apply when service creation is enabled.