Skip to content
Mosayic

FAQ

Is Mosayic free?

Section titled “Is Mosayic free?”

The Mosayic platform itself (the dashboard and the VS Code extension) is free for individual developers. You may pay for the underlying services Mosayic uses on your behalf:

  • Apple Developer Program — $99/year (only if you ship to iOS)
  • Google Play Developer — $25 one-time (only if you ship to Android)
  • Expo / EAS — free tier for builds, $19/mo if you exceed it
  • Google Cloud — free tier covers most early-stage usage; pay-as-you-go after
  • Supabase — free tier (500 MB DB, 50k MAU), $25/mo when you outgrow it

A typical Mosayic project at zero traffic costs ~$0/month. A project with light traffic and one platform shipped costs $25-150/year depending on which paid services you’ve crossed.

Do I own my code?

Section titled “Do I own my code?”

Yes. Your code lives in your GitHub account, in your repos. Mosayic doesn’t fork, mirror, or proxy your code. If you delete your Mosayic account tomorrow, your repos, your databases, and your deployed services keep working.

Can I use Mosayic without VS Code?

Section titled “Can I use Mosayic without VS Code?”

Not currently. The dashboard talks to your machine via the VS Code extension, so VS Code is required.

The extension itself is small (~3000 lines of TypeScript) and could conceivably be ported to other editors. If this matters to you, open an issue — we’ll prioritise based on demand.

Can I use Mosayic with my existing project?

Section titled “Can I use Mosayic with my existing project?”

Not directly. Today, the setup guide assumes a green-field project — Mosayic creates the folder, scaffolds from templates, sets up the GitHub repos.

If you have an existing React Native or Expo project, you can:

  1. Create a new Mosayic project to get the scaffolding
  2. Copy your existing code into the mobile/ folder
  3. Resolve any dependency or config differences

Importing existing repos directly is on the roadmap.

Does Mosayic see my code?

Section titled “Does Mosayic see my code?”

No. The Mosayic backend never sees the contents of your files. The extension reads files locally and uploads results of commands (e.g. gh repo create output), but it doesn’t transmit source code.

Does Mosayic see my secrets?

Section titled “Does Mosayic see my secrets?”

Briefly — through the WebSocket relay when you set them via the dashboard. Secrets are not persisted on Mosayic’s servers. The destination is always Google Cloud Secret Manager, GitHub Actions secrets, or your local .env file.

If you want to avoid even the brief transit, you can set secrets directly with the CLI (gcloud secrets create ... or gh secret set ...) and then click Mark as set in the dashboard.

Why Google sign-in only?

Section titled “Why Google sign-in only?”

Simplicity. Adding email/password auth means handling password reset flows, rate-limiting brute force attempts, secure password storage, etc. Google handles all of that.

If you have a strong reason you can’t use a Google account (corporate IT, etc.) — let us know. We’re not opposed in principle, just haven’t built it.

What happens if Mosayic shuts down?

Section titled “What happens if Mosayic shuts down?”

Your code, your repos, your databases, your deployed services all keep running — none of them depend on Mosayic. The only things you’d lose are:

  • The ability to use the dashboard for new builds and deploys
  • The Setup Guide and Blueprint walkthroughs

You’d continue using your existing repos with git, eas build directly, gcloud run deploy directly, and supabase CLI directly. Mosayic is automation on top of those tools, not a replacement for them.

Can I self-host Mosayic?

Section titled “Can I self-host Mosayic?”

The components are open source: vscode-mosayic, mosayue, mosayic-api. You can run the backend on your own Cloud Run, host the dashboard on your own domain, and configure the extension to point at it via mosayic.environment: custom.

This isn’t a supported configuration today (we don’t write self-hosting docs), but the code is there if you want to.

What’s the relationship to the older Mosayic?

Section titled “What’s the relationship to the older Mosayic?”

The earlier version of Mosayic was an architectural framework — a collection of recommendations and an optional Python “mosaygent” package. It was largely manual.

Mosayic v2 (this version) is a real product: a dashboard + VS Code extension + backend that automates the same setup the older docs walked you through manually. The underlying stack (React Native + Expo + Supabase + Cloud Run) hasn’t changed, but the path from idea to working app is now an order of magnitude faster.

If you set up the older Mosayic by hand, your existing project is still compatible — you can import it once that feature lands.

Why the name?

Section titled “Why the name?”

Mosayic apps assemble from many small pieces — a tile here, a tile there. Push notifications. Auth. Payments. Each one slots into a consistent grid. You end up with a mosaic.

(Also “Mosayic.io” was available.)

Can I contribute?

Section titled “Can I contribute?”

Yes. The three repos are open source. Issues, PRs, and discussions all welcome:

For docs corrections (typos, broken links, wrong information), the easiest path is the Edit this page link at the bottom of each page — it opens a GitHub edit form on this docs repo.

Where can I get help?

Section titled “Where can I get help?”