Backends, auth & databases
Full-stack Chrome extensions, from one prompt
ManifestGo is not limited to popups and client-side logic. It ships complete Manifest V3 extensions with real authentication, a hosted database, encrypted API keys and third-party integrations — wired end to end and verified before you download the .zip.
What “full-stack” means here
Real authentication
Email + password sign up, sign in, sign out, session persistence, and automatic token refresh — rendered as real signed-out and signed-in popup states.
Database reads & writes
Per-user rows via the REST API with filters, inserts, updates and deletes. Your data lives in your own Supabase or Firebase project.
Encrypted secrets vault
Store OpenAI, Anthropic, Google, Stripe or any other key per project. Keys are injected at build time and never surfaced in the UI.
Service-worker backend layer
The MV3 service worker owns tokens, orchestrates API calls, handles alarms and context menus, and returns results to popup and content scripts.
Third-party API integrations
LLM providers, Notion, Slack, Stripe, webhooks — scoped host permissions, retries, AbortController timeouts and visible error states included.
Verified before download
Every build is parsed for syntax errors, MV3 CSP violations, dangling file references and credential leaks in content scripts before you get the .zip.
How the backend is wired
- 01You describe the extension, including the backend it needs ("save highlights per user with Supabase auth").
- 02The architect model produces a build plan covering surfaces, tables, endpoints and permissions.
- 03The builder generates manifest.json, popup, content scripts, options and a service worker that owns all credentials.
- 04Auth and data calls hit your Supabase or Firebase project directly from the service worker — no npm, no CDN, no proxy.
- 05A deterministic verification pass parses every file, repairs the manifest, and blocks credential leaks before packaging.
Extensions people build with a backend
- Highlight and note saver synced to a user account
- Team bookmark manager with shared collections
- AI page summarizer billed against your own API key
- Lead capture tool that writes rows straight to your database
- Job application tracker with cross-device sync
- Usage analytics dashboard backed by your own tables
FAQ
Can ManifestGo build full-stack Chrome extensions?
Yes. ManifestGo builds full-stack Manifest V3 Chrome extensions with a real backend: Supabase or Firebase authentication (sign up, sign in, sign out, persisted sessions), database reads and writes, and third-party API calls. Credentials live in a single config module and the background service worker owns every token, so no key is ever exposed to page context.
Does ManifestGo support Supabase in generated extensions?
Yes. ManifestGo wires Supabase natively without npm or CDN imports — it calls the Supabase Auth endpoints (/auth/v1/signup and /auth/v1/token) and the REST data endpoints (/rest/v1/<table>) directly from the MV3 service worker, persists access and refresh tokens in chrome.storage.local, and refreshes them before expiry. The popup renders the real signed-out and signed-in experiences.
How are API keys and secrets handled?
Every project has an encrypted secrets vault. Keys are injected into a single config module at build time, stored in chrome.storage.local at runtime, and only ever read by the background service worker. Content scripts and popups call the worker via chrome.runtime.sendMessage and receive results, never raw credentials.
Is user data synced across devices?
Yes when your extension uses a hosted database. Sessions and preferences persist in chrome.storage, and records live in your own Supabase or Firebase project, so the same user sees the same data on any machine where they sign in.
Do I own the backend and the code?
Completely. The database is your own project, the credentials are yours, and the extension source ships unminified in a .zip you can publish to the Chrome Web Store under your own developer account.