Products¶
A one-page index of every product in the Zev ecosystem. Click into each for the full profile — what it is, who uses it, what it does, the security posture, and how it cross-integrates with the rest of the ecosystem.
Every product below is operated under ZevOP Technologies Limited. They share a single identity layer (ZevID), a single user account, and a common set of operational controls.
The ecosystem¶
ZevID →¶
The identity layer. One account, one set of credentials, one MFA enrolment — used to sign in to every Zev product. Lives at accounts.zevop.com. Users don't "use ZevID" the way they use the others; they sign up once at any Zev product and a ZevID account is created behind the scenes. Status: Live.
ZevPay¶
Payments. Personal and business accounts, wallets, transfers, and KYC for financial regulation. Status: Live. Profile in preparation.
ZevCommerce¶
Merchant platform. Storefronts, catalogues, and orders for merchants — with ZevPay integrated for collections. Status: Live. Profile in preparation.
ZevCloud →¶
Developer cloud. The first Nigerian-operated managed-deployment platform with full tenant isolation — each customer's service runs in its own container, not sharing CPU, memory, or filesystem with anyone else. Built for teams that have outgrown cPanel-class shared hosting locally and don't want to graduate to USD-billed international platforms. Includes domain registration (direct .ng accredited registrar; non-.ng via registry partner), DNS management, and email forwarding — all from the same dashboard. Naira-billed. Lives at console.zevcloud.net. Status: Live.
ZevSend →¶
Transactional messaging API. Email today (AWS SES under the hood), with SMS, WhatsApp, and OTP-verify on the same team-and-domain model. Built for developers shipping receipts, password resets, shipping notifications, and OTPs from inside their applications — Naira-billed, locally operated, deliberately transactional only. The brand-identity admin approval gate, per-team suppression list, and abuse-driven suspension policies all exist to keep sending reputation tuned for transactional traffic; bulk marketing belongs on ZevCampaign instead. Lives at console.zevsend.com (dashboard) and api.zevsend.com (developer API). Status: Live (email; SMS / WhatsApp / Verify gated on admin-side carrier enablement).
ZevCampaign¶
Marketing messaging suite. Newsletters, broadcasts, drips, lead nurture, and audience segmentation — for marketers, not developers. Sibling product to ZevSend; the two are deliberately separated so transactional and marketing send reputations stay independent. Same Zev account, same Naira-billing, same Zev Credit balance — different operational rules. Status: In planning. Profile in preparation.
ZevWorkspace¶
Organisation collaboration. Teams, documents, and workspace tooling for organisations. Status: Live. Profile in preparation.
How the products cross-integrate¶
Every Zev product authenticates users through ZevID. A user signing up at any one product gets a ZevID account (centrally) plus an enrollment row for that specific product. ZevID accounts are never auto-created at other products — each enrollment is consent-gated and only happens when the user visits that product and signs up explicitly.
Cross-product capabilities (e.g. a Zev product acting on a user's behalf at another) are unlocked by an OAuth-style consent screen on accounts.zevop.com. The user grants explicit permission, per product, per scope. They can review or revoke those permissions at any time from their account portal.
For the user-facing detail of how each product participates in this, see the integration section of each product's profile.
Shared capabilities¶
Beyond shared identity, the ecosystem offers cross-product capabilities every product can participate in:
- Zev Credit — a centralised, non-withdrawable spending balance every ZevID user has. Earn it from one Zev product (refund, referral, signup bonus, etc.), spend it at any product that accepts it.
Each product's profile expands on how that product specifically uses each shared capability.