Connected out of the box
The essentials every app needs are built in — 10 of them, ready the moment you create an app. For everything else, there's a REST API and plain fetch().
What's included, honestly labeled
“Built in” means it works in every app with no setup. “Via REST API” means you connect it yourself using our documented endpoints.
Maker77 AI
Chat, generation, classification and JSON output inside your app — no API key needed.
Cloud database
Per-app collections with filters, sorting, counts and owner-only records.
User auth
Email + password sign-up and sign-in for your app's own users, with persistent sessions.
File storage
Upload images and documents up to 10 MB and get back a public URL.
Emailby Resend
Send transactional email — confirmations, notifications, receipts — from your app.
Paymentsby Stripe
One-off card payments with your own Stripe account via hosted Checkout. Every payment lands in your payments collection.
Hosting & SSL
yourapp.maker77.app on every plan, custom domains with automatic SSL on Starter+.
Analytics
Views, users and records for each published app, in your dashboard.
PWA install
Manifest, icons and service worker generated so apps install to the home screen.
Flutter apps
Generated Flutter projects already use the REST API to read and write the same data.
Native iOS & Android
Call the same endpoints from Swift, Kotlin or React Native with plain HTTP.
Your own backend
Read records, sign users in or call AI from any server or script that speaks JSON.
Webhooks & automation
Signed POST requests on record created/updated/deleted and user sign-ups — plug into Zapier, Make or n8n (Starter+).
AI calls, file uploads and emails from live apps use 1 integration credit each. Database, auth, hosting and analytics are free.
Connect anything else
The web SDK is a thin wrapper over a plain JSON API. Any client can use it — and your app can call any outside service that accepts browser requests.
Same data, any client
GET, POST, PATCH and DELETE records; sign users up and in; call AI. Send the user's token as a Bearer header for per-user data.
Outgoing webhooks with fetch()
Ask maker77 to POST new leads or orders to a Zapier, Make or n8n webhook. The receiving endpoint must accept requests from browsers (CORS).
# list this user's tasks
GET /api/runtime/{appId}/db/tasks?mine=1
Authorization: Bearer <userToken>
# create a record
POST /api/runtime/{appId}/db/tasks
{ "data": { "title": "Ship v2" } }
# sign in
POST /api/runtime/{appId}/auth/signinconst lead = await m77.db.create('leads', form);
await fetch('https://hooks.zapier.com/…', {
method: 'POST',
body: JSON.stringify(lead)
});Endpoint reference in the docs.
We'd rather tell you up front: payments cover one-off Stripe checkouts today (subscriptions are on the roadmap), there are no one-click connectors for third-party SaaS tools, and no social sign-in for app users. You can connect other tools through webhooks or your own server as shown above. Tell us what you need most — it directly shapes the roadmap.
What should we connect next?
Tell us the service and what you'd use it for. We read every request, and the most-requested integrations go to the top of the list.
The backend is already done
Start an app and use AI, data, auth, storage and email from the first prompt.