Every project gets a full stack.

Think of this like a Publish button for your whole project. Mosaic looks at the files in your folder, figures out what kind of site it is, and puts it online — usually in under a minute. There's no separate hosting company to sign up for and nothing to configure.

curl -X POST $API/{slug}/git/files/batch \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{
    "files": [{"path": "index.html", "content": "<h1>Hello</h1>"}],
    "message": "Initial commit",
    "deploy": true
  }'

A database is just a very organized filing cabinet for your app. Instead of papers, it stores rows of information — like a spreadsheet — that your app can search, sort and update instantly. Every sign-up, order or comment someone submits gets saved here automatically.

curl -X POST $API/{slug}/sql \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{
    "query": "INSERT INTO sign_ups (email) VALUES ($1) RETURNING *",
    "params": ["alice@example.com"]
  }'

This is like a shared drive built into your project. Anywhere people need to upload something — a photo, a resume, a PDF — it's saved here instead of getting lost in someone's downloads folder or emailed back and forth.

curl -X POST $API/{slug}/storage/upload \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"filename": "uploads/cat.jpg", "content_type": "image/jpeg"}'
# → {"upload_url": "https://s3.mosaic.site/...", "method": "PUT"}

This is the "who are you?" part of an app. It lets someone create an account and log back in later — by typing a password, clicking a link emailed to them, or signing in with a Google or GitHub account they already have. Nobody has to write any of this by hand.

curl -X POST $API/{slug}/auth/send-magic-link \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"email": "user@example.com",
       "redirect_url": "https://yourapp.mosaic.site/dashboard"}'
# → {"sent": true, "expires_in_minutes": 15}

Every project always gets a free address like bake-sale.mosaic.site. If you want something that looks more official — like bake-sale.cruxosai.com — you attach it to the same project. Nothing moves, nothing gets rebuilt, and the old address keeps working too.

curl -X POST $API/{slug}/domains \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"domain": "bake-sale.cruxosai.com"}'

curl -X PATCH $API/{slug}/domains/bake-sale.cruxosai.com \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"is_primary": true}'

Your app can send real emails by itself — a "you're invited", a receipt, a password reset — without anyone opening an email program. It arrives from your own address, like no-reply@yourcompany.com. (Needs a Mosaic Pro plan and a verified sending domain.)

curl -X POST $API/{slug}/mail/send \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{
    "to": ["client@example.com"],
    "subject": "You are invited!",
    "html": "<p>Saturday at noon.</p>",
    "from_addr": "no-reply@mycompany.com"
  }'

Normally a webpage only updates when you refresh it. This — what Mosaic calls Realtime — makes it update itself the instant something changes, like watching a live scoreboard or seeing a teammate check off a task without anyone hitting refresh. (Needs a Mosaic Pro plan.)

const ws = new WebSocket(
  `wss://api.mosaic.site/v1/project/${slug}/realtime?apikey=${KEY}`
);
ws.onopen = () => ws.send(JSON.stringify(
  { type: "subscribe", table: "tasks", event: "*" }
));
ws.onmessage = (e) => console.log(JSON.parse(e.data));

A short-term memory for the app — much faster than the database, for things that don't need to last forever. Like remembering "this person is already logged in" for the next hour, instead of checking every single time. (Needs a Mosaic Pro plan.)

curl -X POST $API/{slug}/redis/incr \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"key": "page:views", "amount": 1, "ttl": 86400}'

Every time you publish an update, Mosaic keeps the old version too — like an Undo button for your entire website. And "archiving" a project is like putting a box in storage instead of the trash: everything is kept exactly as it was, and you can bring it back anytime.

curl -X POST $API/{slug}/deploy/rollback \
  -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"version": 4}'

curl -X POST $API/{slug}/archive -H "X-API-Key: $KEY"