Email us
Questions, bugs, anything that is not working the way these pages say it should. Tell us your project’s reference (the short code in its address, /p/…) and what you expected.
Support
Help, from the people who build it.
We are a small team, and the person who reads your message is the person who can fix the problem. We would rather you write early than lose an afternoon to something we can sort out in minutes.
Is it us?
The status page shows whether the platform is up. If something has stopped working for everyone, it is there before it is in an email.
Need an invite?
Sign-up is invite-only during early access. Tell us what you are building and we will send a code.
Found a security problem?
Please tell us privately first, and give us a reasonable chance to fix it. Describe what you found and how to reproduce it; do not access data that is not yours. We will thank you and tell you what we did.
What to expect
Honest about how fast, and how.
There is no formal response-time commitment yet. An uptime and support commitment is planned for the Business plan, not before. What we can promise is that every message is read by someone who builds the platform, and that we will tell you plainly if something is a bug, a limit, or a thing we have not built.
To help us help you, include
- your project reference, and the page or call that failed;
- what you expected, and what happened. Error messages carry a
codeand aresolution: paste both; - roughly when, with your time zone. The request log under Pulse shows the request, and we can look at it with you;
- for a code problem, the smallest example that shows it. Never send a secret key or a password; if you did by accident, tell us and rotate it.
Common questions
Before you write.
The sign-in code never arrives by SMS.
Real SMS delivery is not switched on yet. While you build, use a test number: under Authentication → Providers → Test OTPs you can set a phone number and a fixed code. Live SMS is next, and needs a provider account.
I can’t sign up; it asks for an invite code.
That is early access. Ask for a code and tell us what you are building.
An email code or link, or a password reset, didn’t arrive.
Password sign-in and test phone numbers work everywhere. Email codes and links depend on mail delivery being switched on for the environment you are in. If one doesn’t arrive, tell us your project and we will check.
A request failed and I don’t know why.
Open Pulse in the dashboard and find the request in the log. Every error carries a code, a message and a resolution, which says what to try next. If the resolution doesn’t help, send us all three.
How do I get my data out?
Your project is a plain Postgres database, and Settings → Database has its connection string, so you can use pg_dump. A one-click export in the dashboard is not built yet. If you hit a snag, write to us and we will help you move.
Can I get the SDK or the CLI?
The SDK is on npm: npm install @affineq/js, and @affineq/ssr for server-rendered apps. The command line is not distributed yet; ask us for a build.
Where is my data stored?
In London today. We say that plainly because it matters. An African region comes when a customer needs it, starting with Johannesburg.
Still stuck? Write to us.
A short message with the project reference is enough to start.