AffinEQ

Product

Platform overview Integrations Verified, not claimed What isn't built yet

Solutions

Mobile-first startups Agencies building for SMEs Fintechs & regulated teams What people build

Migrate

How a move works From Supabase From Appwrite From Firebase From AWS Amplify From any Postgres Pricing

Developers

Documentation Next.js quickstart JavaScript quickstart Changelog Support Contribute Platform status

Company

Why we exist Customers Blog Partners Contact Sign in Start building
Partners

Be where African developers start.

Every new app on AffinEQ needs a way to get paid, to send a message, to know who a user really is. If you provide that, we’d like developers to find you inside the platform, set up in a minute, with their own credentials and your name on it.

Two ways in

A template anyone can submit. A provider only we build.

The difference is where the code runs, and we keep it that way on purpose.

Worker templatePlatform provider
What it isA function, a docs page and a checklist of the secrets it needs. Examples: a payment processor, an SMS gateway, a KYC check, a delivery API.A route built into AffinEQ itself, such as the SMS gateway behind phone sign-in, a mobile-money top-up, or a storage backend.
Who builds itYou can submit one, or we’ll write it with you. We review every template.We do, from your API documentation and a sandbox account. Your code never runs inside our platform.
Where it runsIn the developer’s own project, in the Workers sandbox, with their credentials and nothing of ours.Inside the AffinEQ control plane, which is why we write and own it.
How developers use itInstall from the directory, paste their secrets, done.A switch and a credentials form in the dashboard.

On payments, one rule applies to everyone: we never hold the money. A payment integration runs on the developer’s own account with your service, so AffinEQ is never a party to the funds.

How it works

From a conversation to a listing.

  1. ApplyTell us who you are, what the service does and who needs it. Five minutes.
  2. We talkA real reply from someone who builds the platform, usually with questions about your API.
  3. We build and testWe run the integration against your sandbox, the way we run our own example app against production.
  4. You’re listedA page in the directory, kept honest: if your API changes and the template breaks, it says so until it’s fixed.

The public directory opens when there are enough integrations to make it worth visiting. Applying now puts you at the front of it.

What kind of integration?
Can we test against a sandbox?
A listing is a promise that it works. We need to know who keeps it.

This opens a draft in your own mail app, addressed to the partnerships team. Nothing is sent until you press send, and nothing is stored by this page.

Type to search. Nothing you type leaves this page.