DPS — Duaba Platform Services
The platform authority for all Duabalabs services.
DPS (Duaba Platform Services) is the centralized control plane that hosts, provisions, and orchestrates every backend Duabalabs operates — including Sellub, 3y3anaa, the donation/subscription landings, and any future product. If a Duabalabs app needs Parse Server hosting, multi-tenant data isolation, Paystack-backed checkout, or Docker-based deployment, it goes through DPS.
Surfaces
| Surface | URL | For |
|---|---|---|
| Marketing site | dps.duabalabs.com | Prospective customers |
| Platform dashboard | platform.duabalabs.com | DPS customers managing their hosted apps |
| API ingress | api.platform.duabalabs.com | Hosted apps’ backends + the dps-client SDK |
| Parse dashboard | api.platform.duabalabs.com/dashboard | Operators (schema, classes, cloud code) |
What DPS provides
- Multi-tenant Parse Server hosting — one isolated MongoDB + Parse instance per customer app.
- Template-driven provisioning — wizards that scaffold parse-server, sellub, react-web, react-native, and n8n apps end-to-end.
- Docker registry & orchestrator — private images on
ghcr.io/duabalabs, deployed via Docker SSH or Netlify/Vercel. - DPS-E module — shared E-commerce ops layer (Billing, Payments, Logistics, Social) that Sellub and integrators consume.
- Checkout pipeline — DPS → Paystack → tenant subaccount, with
directandvendureflows. @duabalabs/dps-clientSDK — single npm package every consumer app uses to talk to DPS.- n8n workflows — automation glue (
dps-workflows).
Sections
ArchitectureSupported App TypesMulti-Tenancy & IsolationDPS AppsTemplatesPricing TiersClient OnboardingSellub on DPSAPI ReferenceDeployment
Source repos
- duabalabs/dps — umbrella submodule
- duabalabs/dps-server — Parse Server + DPS-E
- duabalabs/dps-dashboard — Next.js 14 + Refine
- duabalabs/dps-templates-parse-server
- duabalabs/dps-templates-react-landing
- duabalabs/dps-templates-react-nextjs
- duabalabs/dps-templates-react-native
- duabalabs/dps-workflows
Source-of-truth docs
These structured chapters consolidate material from the in-repo source docs: