White-Label & Branding
Nothing in the product signals DeliveryStack to your customers, your partners, or your vendors. The brand on every touchpoint is yours, and so is the asset it lives on.
Integrations
Twenty-four connectors ship configured. Anything outside the list is built against the same interface, per region.
Security & Compliance
Payment, privacy, and health-data obligations differ by market. The platform is configured to the regimes you actually operate under.
API & Docs
A REST API over the same objects the apps use, webhooks on every state change, and a public reference your developers can read before signing anything.
# create an order on behalf of a vendor
curl -X POST https://api.yourbrand.com/v1/orders
-H "Authorization: Bearer $KEY"
-d '{"vendor_id":"v_18f2","items":[…],
"drop":{"lat":12.971,"lng":77.641}}'
# webhook fired on every state change
order.assigned → { id, partner_id, eta }
order.completed → { id, proof, total } Platform-Wide FAQ
Ownership, compliance, and what your developers can reach.
Still have questions? Talk to our team
Does white-label mean a skin, or real ownership? +
Real ownership of the customer-facing assets. Apps are published under your developer accounts, the domain is yours, and the install base and data stay with you if the engagement ends. Aalpha's name appears nowhere your customers can see it.
What if the integration we need isn't in the 24? +
Most requests are a connector against the same interface rather than platform work. Send us what you run — payment processor, POS, accounting system — and we'll tell you whether it's configuration, a connector build, or genuinely custom.
Are you certified for PCI DSS and SOC 2? +
Card data is handled by certified gateways, so the platform stays out of the card-storage scope. For GDPR, RBI, SAMA, and HIPAA-aligned deployments we configure residency, retention, and access controls to the regime, and document the setup for your auditors.
Can our developers build on top of the platform? +
Yes. The REST API and webhooks cover the same objects the apps use, and a sandbox with seeded data is available before production access. The reference is public — your team can read it before you commit to anything.
Who owns the data we generate? +
You do. It lives in a database instance dedicated to you, in your chosen region, and is exportable in full in standard formats at any point, including at the end of the engagement.
Bring Us Your Requirements List
Send the integrations you need, the regimes you operate under, and the systems you already run. We'll come back with what is configuration, what is a connector, and what is custom work.