Your app can talk to the things you already pay for
114 services, and you bring your own account with each one. Ask for the one you need while your app is being built — it gets wired in, and you paste the key once.
Taking payments
Card, UPI, netbanking and wallets, through the payment company you already have an account with.
Mercado Pago payments (Latin America)
Take payments across Latin America, including Pix and local cards.
Build with thisXendit payments (Southeast Asia)
Take payments across Southeast Asia, including local e-wallets.
Build with thisSMS and WhatsApp
One-time passwords, order updates and reminders, sent to a phone rather than an inbox.
WhatsApp Cloud API (Meta)
Send order updates, booking reminders and replies on WhatsApp.
Build with thisOnline stores
Your store's products, orders and customers, in a custom app for your team or your buyers.
Social media
Your posts and messages, shown and handled inside your own app.
Sending mail your app actually needs to send — receipts, resets, invitations.
Gmail (Google Workspace)
Send and read email from your own Gmail or Google Workspace account.
Build with thisNotifications and live updates
Push notifications to a phone, and screens that change without anyone reloading them.
Sign-in and backends
Letting people sign in with an account they already have, and services that store data for you.
Photos, files and video
Storing what people upload, resizing images, and putting live or recorded video on a page.
Maps and addresses
Showing a location, finding an address as someone types it, and working out a route.
AI services
Services your own app can call — writing, images, speech, translation. Separate from what we use to build your app, which is our side of the arrangement, not something your app pays for.
Analytics
Seeing what people actually do in your app, in a tool you own the data in.
Spreadsheets and databases
Reading and writing the sheets and boards a team already runs on.
Team chat
Posting into the channels your team is already watching.
Business tools
Accounting, sales pipelines and customer support, connected to what your app knows.
Shipping
Booking pickups and tracking what has gone out.
Identity and signatures
Verifying who someone is, and getting a document signed.
Bookings
Letting people pick a time without anyone going back and forth about it.
Search
Search that keeps up as someone types, over more records than a database query wants to scan.
Data and content
Weather, news, photography, film listings and public data, for apps that show the world rather than record it.
How connecting one works
Every service here is yours, not ours. You keep your own account with the company, on your own terms and your own bill — we never resell anything, and we never see what you spend with them.
When your app needs one, it asks you for the key, once. You paste it in and nobody, including us, can read it back afterwards — there is no screen anywhere that shows it and no way for us to look. Your app reads it while it runs.
Saying no is a real answer. The rest of the app carries on being built without it, and you can add the key later.
If what you need is not here
Ask for it anyway. Your app can only reach the services on this list, which is what stops an app from quietly calling somewhere it should not — so a new one gets read by a person here before it is switched on. That takes as long as it takes; we would rather tell you that than pretend the list is infinite.
Describe the app. Connect it to what you already use.
You do not have to decide any of this up front. Start with the app, and add the services when you get to the part that needs them.
Start buildingOr read how it works first.