GuideNext.js
Sign-in that a Server Component can read, with the proxy that keeps it fresh. The App Router, end to end.
Documentation
Start from your framework.
Short guides that end with a table you can read and a user who can sign in. Where a guide does not exist yet, the card says so, and the plain HTTP API works from anything in the meantime.
Quickstarts
Pick what you build with.
Every card says what is true today. Guide has its own page; Use the JS guide works with the JavaScript client; Planned is not built yet.
Guide
GuideJavaScript & TypeScript
Install the client, read and write a table, sign a user in by phone. Node, browsers, Deno, Bun and edge runtimes.
Use the JS guideReact
Works today with the JavaScript client, which has no framework dependency. Start with the JavaScript guide.
Use the JS guideVue
Works today with the JavaScript client, which has no framework dependency. Start with the JavaScript guide.
Use the JS guideNuxt
Works today with the JavaScript client, which has no framework dependency. Start with the JavaScript guide.
Use the JS guideSvelteKit
Works today with the JavaScript client, which has no framework dependency. Start with the JavaScript guide.
Use the JS guideAstro
Works today with the JavaScript client, which has no framework dependency. Start with the JavaScript guide.
Use the JS guideSolidJS
Works today with the JavaScript client, which has no framework dependency. Start with the JavaScript guide.
Guide plannedExpo (React Native)
The client takes a storage adapter, so a session can live in the device’s own storage. A guide is planned; the JavaScript guide covers the rest.
PlannedFlutter
A Dart client is planned. Until then every call is plain HTTP, which Dart can make: see the REST example below.
PlannediOS (Swift)
Not yet. Plain HTTP works from Swift today.
PlannedAndroid (Kotlin)
Not yet. Plain HTTP works from Kotlin today.
PlannedPython
Not yet. Plain HTTP works from any Python HTTP library.
PlannedPHP & Laravel
Not yet. Plain HTTP works from PHP and Laravel today.
Anything that can make an HTTP request
No SDK needed to start.
Your project’s Postgres is an HTTP API. The publishable key names the project, so there is nothing else to configure.
curl "https://api.affineq.com/rest/v1/todos?select=*" \ -H "apikey: aq_pub_..."
Client libraries
What exists, and what does not yet.
@affineq/js
The client for JavaScript and TypeScript: data, auth, storage, live updates and Workers. MIT licensed, no runtime dependencies. If you have used the Supabase client, your hands already know it. npm install @affineq/js
@affineq/ssr
Cookie sessions for server-rendered apps: Next.js and anything else that reads a user before the browser runs. Read it before changing how a session is stored.
The CLI
Push migrations, deploy Workers and manage a project from a terminal or a pipeline, with a personal access token. The CLI reference.
Dart, Swift, Kotlin, Python
Planned, in the order the apps that are waiting need them. The HTTP API is the same one the JavaScript client calls.
Guides
Then go deeper.
Data
Reading and writing your tables, embedding, functions, row-level security.
Authentication
Phone codes through your own SMS provider, email and password, magic links, and fifteen social providers.
Storage
Files with the same policies as your tables, on our servers or your own bucket.
Live
Changes to a table, pushed to the people looking at it.
Workers
Server code next to your data, with secrets it holds.
Coming from Supabase
What changes in your code, and how a move is run. The migration guide.
Looking for SMS, payments or storage providers? Mobitech, Africa’s Talking, M-Pesa, Paystack, eCitizen and the cloud storage options are on the integrations page, with where each works and what is built.