Going live

Your Riggr Spark app starts on your computer (localhost). That is enough to try it yourself. Deploy only when you want teammates (or yourself on another device) to open it on the public internet with a real https:// address.

You do not need to become a DevOps engineer. The easy path is: put the code on GitHub → connect Vercel (it gives you HTTPS for free) → optionally point a GoDaddy (or any) domain at Vercel.

Prefer a chat coach? Copy the prompt below into Claude Code, Cursor, or Codex (the tool that already has your app folder) and ask it to walk you through each step.

I'm a Shopify merchant using Riggr. I'm not a developer. My Spark app already runs on localhost. Help me deploy it to a public HTTPS site the easiest way possible.

Walk me one step at a time, wait for my reply before the next step, and explain every click in plain language.

Follow this Riggr Going live checklist exactly:
1) Create a free GitHub account if I don't have one (https://github.com).
2) Put this app's folder on GitHub (you create the repo and push — ask before anything destructive).
3) Sign up for Vercel with GitHub (https://vercel.com) and Import the repo. Use Next.js defaults.
4) Add my Riggr env vars from .env.local into Vercel Project Settings → Environment Variables (RIGGR_API_KEY, RIGGR_API_URL, RIGGR_PROJECT_ID). Redeploy after saving.
5) Confirm the free vercel.app HTTPS URL loads the app.
6) Optional custom domain: in Vercel → Domains, add my domain (example: apps.mystore.com). At GoDaddy DNS, add the CNAME (or A records) Vercel shows. Wait for DNS, then confirm https:// works with the lock icon.
7) Tell me clearly what still only works on localhost (e.g. laptop SQLite) and what I should ask you to harden next (hosted database, real user login if the Spark needs multiple people).

Official Riggr Help: https://www.hiriggr.com/help/going-live
If something is about Shopify connect, MCP, or API keys, point me to Riggr Help / in-app support instead of guessing.

When you need this

| Situation | Stay on localhost | Go live | |-----------|-------------------|---------| | Trying a Spark yourself | ✓ | | | Iterating with your AI | ✓ | | | Teammate on another network needs the same app | | ✓ | | You want a bookmark like https://ops.yourbrand.com | | ✓ | | Sparks that need real multi-person login (e.g. Staff Live Chat for remote staff) | demo locally first | ✓ + ask AI for real auth |

Easy path overview

1. GitHub — free home for your app’s code (like a cloud backup your deploy tool can see).
2. Vercel — free HTTPS hosting that understands Next.js (what Riggr Sparks use). One click import from GitHub.
3. Domain (optional) — keep the free something.vercel.app URL, or point a name you own (GoDaddy example below) at Vercel.

You can stop after step 2 and still have a real public HTTPS site.

1. Put the app on GitHub

1. Create a free account at github.com if you do not have one.
2. In your coding AI, say: “Create a private GitHub repo for this app and push the code. Do not commit .env.local or secrets.”
3. Confirm the repo appears on GitHub and does not show your API key.

2. Deploy on Vercel (public HTTPS)

1. Go to vercel.com and Continue with GitHub.
2. Add New… → Project → Import your repo.
3. Leave the Next.js defaults. Click Deploy.
4. When it finishes, open the *.vercel.app URL — that is already HTTPS.

Add your Riggr API key on Vercel

The live site needs the same values as local .env.local:

| Name | Where it came from | |------|--------------------| | RIGGR_API_KEY | Project → API key download | | RIGGR_API_URL | Usually https://www.hiriggr.com/api/v1 | | RIGGR_PROJECT_ID | Same download file |

In Vercel: Project → Settings → Environment Variables → add each for Production (and Preview if you want). Redeploy after saving.

Ask your AI: “Read my local .env.local names (not values in chat if you prefer) and tell me exactly what to paste into Vercel.”

3. Custom domain with GoDaddy DNS (optional)

You can keep your-app.vercel.app forever. If you want something like apps.yourstore.com:

1. In Vercel → Project → Settings → Domains, add your domain (or subdomain).
2. Vercel shows the DNS records to create (usually a CNAME for a subdomain, or A records for an apex domain).
3. At GoDaddy (or whatever registrar you use): open the domain → DNS → Add the record(s) Vercel listed.
4. Wait for DNS (often minutes; sometimes up to 24–48 hours).
5. Back in Vercel, wait until the domain shows Valid. Open https://… and confirm the browser lock icon.

Example (subdomain): if Vercel asks you to point apps to cname.vercel-dns.com, in GoDaddy you add:

| Type | Name | Value | TTL | |------|------|-------|-----| | CNAME | apps | cname.vercel-dns.com | 1 hour / default |

(Use the exact host and value Vercel shows — do not invent them.)

After deploy — what to harden next

Deploy gets you a public HTTPS URL. Some Spark defaults still assume a laptop:

• SQLite on disk — fine for solo local use; for a real team on Vercel, ask your AI to move chat/notes to a hosted database.
• PIN / display-name “login” (e.g. Staff Live Chat Kickstart) — fine for two browsers on one machine; for remote staff, ask your AI to add real user authentication.
• Secrets — rotate a Riggr API key in the dashboard if it was ever pasted into chat or committed by mistake.

Hand your AI a plain ask: “We’re live on Vercel at <URL>. Move local SQLite decisions to a hosted DB and add real login so my team can use this safely.”

Common hiccups

What you can ignore for now

You do not need Docker, Kubernetes, or a dedicated server. You do not need to deploy to get value from Riggr — localhost is the default. Use this page when a public HTTPS link (and optionally your own domain) becomes the goal.

Next steps

• Your computer setup — Terminal, Node, npm run dev
• Sparks — project map and Autopilot
• Setup guide — API key and MCP
• Troubleshooting — connection and billing issues