White-label: branding, custom domains and reseller accounts
Offer Pushizo under your own brand: your product name, logo and colors in the dashboard and system emails; the dashboard, tracking links, preference center and status page on your own domains; sub-customer…
Offer Pushizo under your own brand: your product name, logo and colors in the dashboard and system emails; the dashboard, tracking
links, preference center and status page on your own domains; sub-customer management and consolidated
billing for agencies. Decisions: docs/adr/0032-hucre-mimarisi-white-label-bayi.md.
| Feature | Plan |
|---|---|
| Branding (name, logo, colors, support email) and custom domains | Growth and Enterprise (white_label) |
| Hiding the "Powered by Pushizo" notice | Enterprise (hide_powered_by) |
| Reseller account (sub-organizations, consolidated statement) | Enterprise (reseller) |
1. Branding
From the Organization → Branding page or with the API:
PUT /internal/v1/orgs/:orgId/branding
{ "product_name": "Acme Push", "primary_color": "#112233", "secondary_color": "#445566",
"support_email": "destek@acme.com", "hide_powered_by": true }- Colors are
#RRGGBB; sendnullto remove a field. Theeffectivefield in theGETresponse is the result after plan features and (for a sub-organization) the reseller's branding are applied. - Logo:
PUT /internal/v1/orgs/:orgId/branding/logo(multipartfile) — PNG, JPEG or WebP, at most 512 KB. The file type is validated from its contents; SVG is not accepted (it can carry scripts). The logo is served fromGET /branding/v1/logos/:orgId/:file; when a new logo is uploaded, the old one is deleted. You can also provide an externalhttpsaddress withlogo_url. - System emails (invitations, usage/trial warnings, channel and webhook health notifications, data warehouse errors; plus password reset and email verification when the request came from a branded dashboard domain) go out with your branding: product name, logo, primary color, support address; links point to your active dashboard domain. "Powered by Pushizo" is removed only if your plan allows it and you have chosen to hide it.
- If a sub-organization has no branding of its own, the reseller's branding is used.
2. Custom domains
Supported types:
| Type | What is served |
|---|---|
dashboard | Branded dashboard (login, sign-up and all screens) |
tracking | Open/click tracking, unsubscribe and preference links (/t/…) |
preference_center | Subscription preference center and unsubscribe (/t/p, /t/u) |
status_page | Status page (/status, /status.json) |
To add one: Organization → Custom domains → Add, or
POST /internal/v1/orgs/:orgId/custom-domains
{ "kind": "dashboard", "hostname": "panel.acme.com" }
→ 201 { "id": "cdm_…", "status": "pending",
"verification": { "txt_name": "_pushizo-challenge.panel.acme.com", "txt_value": "hs-verify=…",
"cname_target": "edge.eu.pushizo.com" } }Add two records to your DNS:
| Record | Name | Value |
|---|---|---|
| TXT | _pushizo-challenge.panel.acme.com | hs-verify=… (the txt_value from the response) |
| CNAME | panel.acme.com | the cname_target from the response |
Statuses: pending → (TXT verified) verified → (CNAME also correct) active. The check runs automatically every 5 minutes;
if you don't want to wait, call POST …/custom-domains/:id/verify. A domain that cannot be verified within 72 hours, or whose TXT record is deleted,
becomes failed (re-verifying restarts the timer). last_error: txt_missing, txt_mismatch, cname_missing,
cname_mismatch, dns_error.
- The TLS certificate is obtained automatically (ACME) on the first request after the domain becomes
active; no further action is needed. - A domain can belong to only one organization across all regions (409 if it is registered in another organization). At most 20 domains per organization; IP addresses, single-label names, ports and the platform's own domains cannot be used.
- Security: on a domain of a given type, only that type's paths are open; tracking/preference center links only work if they belong to the domain's organization (or the reseller's sub-organizations). Session-authenticated changes made on a branded dashboard are only accepted for that domain's organization (and the reseller's sub-organizations).
- After a region migration, update the CNAME to the new region's target (Data residency).
3. Reseller account
A reseller (Enterprise + reseller) creates and manages sub-organizations. Sub-organizations are separate tenants; their data
is isolated from each other and from the reseller. A single level is supported (a sub-organization cannot be a reseller).
| Action | Endpoint (permission org.manage) |
|---|---|
| List / create sub-organizations | GET / POST /internal/v1/orgs/:orgId/reseller/children (name, optional slug, plan_code) |
| Suspend / resume | POST …/children/:childId/suspend (reason), POST …/children/:childId/resume |
| Take / release support access | POST / DELETE …/children/:childId/support-access (role: admin | viewer) |
Monthly statement (permission billing.manage) | GET …/reseller/statement?month=YYYY-AA |
- The owner of a new sub-organization is the reseller member who performs the action; the default plan is
starter, with no trial period. A reseller cannot assign a sub-organization a plan higher than its own (400,details.max_plan_code). - Suspension: a reseller can only lift suspensions it placed itself (reasons prefixed with
reseller:); suspensions placed by the platform belong to the support team. - Support access is a revocable membership in the sub-organization and is written to the audit logs of both the reseller and the sub-organization.
- Billing is consolidated through the reseller: a sub-organization has no payment flow of its own (
409 reseller_managed). The statement gives, for each sub-organization, the plan price and usage (messages sent, events, API requests; the month's peak active subscribers and MAU) along with totals. - Sub-organizations are created in the same data region as the reseller; an organization in a reseller hierarchy cannot be moved to another region on its own.
Bot protection (Cloudflare Turnstile)
Protecting sign-up, password reset and verification email resend with Cloudflare Turnstile — environment variables, dashboard behavior, API errors, CSP and the disabled state.
Security review — OWASP ASVS 4.0 (Level 2) checklist (Phase 14)
Date: 2026-10-13. Scope: API (apps/api), worker, dashboard, SDK endpoints, data layer. Each item is tied to evidence verified in the code (file/test); "partial"/"open" items are tracked before go-live in GO_LIVE_CHECKLIST.md.…