The mother brand. Onboarding, payments, escrow, and reconciliation tying the ecosystem together.
NID verification, liveness, consent, AML.
BDT payroll, attendance, compliance, workforce AI.
Inventory sync, demand heatmaps, outlet APIs.
Pentest, audit, threat intel, managed SOC.
Logistics + ops layer for merchants and fleets.
Single onboarding for merchants, employees, entities.
Channel program, referrals, integrator network.
What "shared" actually means
Most "ecosystems" are just a marketing page on top of seven disconnected SaaS products. Ours isn't. Four layers are physically shared across every product in the family.
Shared backend
One RLS-secured Postgres + storage tier. Every product reads identity, consent, and entity records from the same source of truth — no integration glue, no drift.
Shared auth & keys
One API key namespace, one IAM model. A merchant signed in to merchant.bd is signed in to kyc.bd, hrtech.bd, and the rest by default.
Shared audit log
Every verification, payment, payroll run, and admin action lands in the same append-only audit stream. One subpoena response covers the whole stack.
Shared event bus
A verification on kyc.bd can trigger payroll eligibility on hrtech.bd, escrow release on 1pay.bd, and risk re-scoring on cyber.bd — without bilateral integrations.
End-to-end: one merchant, five products, zero re-onboarding
How a single onboarding on merchant.bd cascades through the ecosystem without the customer ever repeating themselves.
- 1
Merchant signs up on merchant.bd
One form. KYB + KYC + bank attachment + cyber posture baseline. All seven products provisioned with scoped access.
- 2
kyc.bd verifies the principals
NID + liveness + AML for every director and beneficial owner. Consent receipts archived for the lifetime of the relationship.
- 3
hrtech.bd onboards staff
Each employee re-uses the same KYC.bd identity record. No second selfie, no second ID scan. Payroll is BDT-native and Bangladesh-Bank-aligned out of the box.
- 4
outlets.bd + 1pay.bd start moving money
Every transaction is signed against the verified merchant identity. Reconciliation, settlement, and tax reporting inherit the trust layer.
- 5
cyber.bd watches the whole surface
Audit logs from every product feed one SOC. Anomaly on payroll triggers re-verification on identity. The stack defends itself.
You can also use KYC.bd standalone
If you only need identity — that's fine. KYC.bd ships as a standalone REST API with its own dashboard, billing, and SLA. You can adopt the rest of the ecosystem when (and only when) it earns its place in your stack.