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
Contribute

Help build the backend your own work needs.

A tool for African builders should be shaped by them. You do not have to write our code to make AffinEQ better: the most useful things people give us are integrations, examples, corrections and honest reports from real use.

Where our code is open, and where it isn’t. The platform itself is not open source: we think trust comes from making lock-in impossible (standard Postgres, a standard storage API, your data on request), not from the licence. The JavaScript SDK is MIT-licensed. We will say here, in plain words, when any other part opens up. Until then, the ways to contribute below are the real ones.
Ways to help

Seven things that actually move us.

Build an integration

If you run a payment processor, an SMS gateway, an identity or KYC service, or a startup developers keep rebuilding, apply to be an AffinEQ integration.

Become a partner →

Share a Worker template or an example

An M-Pesa STK-push worker, a delivery-fee calculator, a receipt generator: anything you wrote twice. We review it, credit you, and list it when the directory opens.

Send it to us →

Fix the docs

Tell us where you got stuck, what a page assumed, what was wrong. A confused first hour is the best documentation bug report there is.

Read the docs →

Help with languages

We would like the docs in Swahili and French first, then others, written by people who build in them rather than machine-translated. If you can help, say which language.

Offer to help →

Build with Flutter

A Flutter and Dart SDK is the next client we want, because that is how many African mobile apps are built. If you ship Flutter apps, we want to design it with you.

Talk to us →

Be a design partner

Build something real on early access and tell us where it hurt. We choose what to build next by what real apps run into, so your friction is our roadmap.

Tell us what you’re building →

Write for the blog

If you have built something here that others would learn from, a hard bug, a design you would change, a cost you cut, we would like to publish it, under your name.

Pitch us a post →

How we treat what you give us

Credit, and a straight answer.

  • You are credited by name, or company, wherever your work is shown, unless you ask us not to.
  • You get an answer. If we will not use something, we say why, so it is not a silent no.
  • We do not take your customers’ data or your keys. Send us the smallest example that shows the idea, never a production secret.

We have not set up a formal contributor process, because there are not enough of us to run one well yet. We would rather talk to you.

Not sure where you fit? Write to us.

Tell us what you do and what you would like to see. It is a conversation.

Type to search. Nothing you type leaves this page.