pockethost
PocketHost is an open-source multi-tenant hosting platform for PocketBase that allows you to run hundreds of isolated PocketBase instances on a single server or distributed infrastructure. It provides per-instance subdomains, automatic SSL, custom domain support, and Docker-based deployment.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | pockethost/pockethost |
| Owner | pockethost |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 1.4k |
| Forks | 121 |
| Open issues | 4 |
| Latest release | Unknown |
| Last updated | 2026-07-03 |
| Source | https://github.com/pockethost/pockethost |
What pockethost is
Built in TypeScript, PocketHost wraps PocketBase in a multi-tenant architecture with firewall, edge daemon, FTP/SFTP access, and health monitoring. Deployment options include single-server and distributed edge network topologies via CLI commands (mothership, edge:daemon, syslog).
Get the pockethost source
Clone the repository and explore it locally.
git clone https://github.com/pockethost/pockethost.gitcd pockethost# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Docker and Kubernetes/orchestration knowledge for production multi-server deployments; single-server setup is simpler but limits scale.
- Data isolation model depends on understanding PocketBase instance segmentation; misconfiguration could lead to cross-tenant data leaks.
- Infrastructure costs scale with number of instances and edge nodes; cost modeling and capacity planning are critical.
- CLI-driven operations (firewall, mothership, edge:daemon) imply custom automation; no documented control plane UI or API mentioned.
- SSH key-based access on port 2222 for FTP/SFTP suggests manual key management; assess key rotation and access control workflows.
When to avoid it — and what to weigh
- Single-Instance PocketBase Needs — If you only need one PocketBase instance, PocketHost's multi-tenant overhead and complexity add unnecessary layers; deploy PocketBase directly.
- No Docker/Container Experience — PocketHost requires Docker proficiency and familiarity with distributed systems (firewall, edge daemons); teams without this expertise will face steep learning curves.
- High SLA/Compliance Requirements — No documented SLAs, disaster recovery procedures, or compliance certifications mentioned; unsuitable for regulated industries without significant hardening.
- Vendor-Locked Enterprise Scale — If you require production support contracts, guaranteed uptime SLAs, or vendor accountability, the open-source model and lack of commercial tiers may not fit.
License & commercial use
MIT License: permissive, OSI-compliant. Permits commercial use, modification, and distribution with attribution and no warranty. No GPL obligations.
MIT allows commercial use without royalties or license fees. However, you are responsible for providing your own support, SLAs, and maintenance. No commercial entity or vendor guarantees are attached; this is community-maintained code. If launching a commercial service, budget for internal engineering support and liability insurance.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Docker-based isolation and automatic SSL noted. Key considerations: (1) multi-tenant data isolation correctness—audit PocketBase instance segmentation; (2) SSH key management on port 2222—ensure secure key distribution and rotation; (3) no third-party security audit or vulnerability disclosure policy documented; (4) firewall and edge daemon implementations require review for network segmentation and DDoS/abuse prevention; (5) assess compliance needs (GDPR, HIPAA) independently.
Alternatives to consider
PocketBase (Direct)
If you only need single or few instances, skip PocketHost and self-host PocketBase directly; simpler, lower overhead.
Supabase or Firebase
Managed, multi-tenant BaaS platforms with commercial support, SLAs, and compliance certifications; lower operational burden at higher cost.
Railway, Render, or Fly.io (with custom orchestration)
Platform-as-a-Service providers with simpler container deployment; host PocketBase instances without building multi-tenant infrastructure.
Build on pockethost with DEV.co software developers
Evaluate PocketHost for your multi-tenant backend needs. Start with the quickstart, review architecture docs, and join the Discord community. For production SLAs or managed hosting, explore pockethost.io or consider alternatives like Supabase.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
pockethost FAQ
Can I host PocketHost in production with SLA guarantees?
What is the typical cost to run PocketHost for 100 instances?
Does PocketHost support automatic data backups?
Can I migrate from Supabase or Firebase to PocketHost?
Work with a software development agency
Adopting pockethost is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.
Ready to Deploy PocketBase at Scale?
Evaluate PocketHost for your multi-tenant backend needs. Start with the quickstart, review architecture docs, and join the Discord community. For production SLAs or managed hosting, explore pockethost.io or consider alternatives like Supabase.