Skip to main content
You install Magic Meal Kits from the web app at make.magicmealkits.com — a one-click wizard deploys the MMK image into your own Google Cloud project. You own the deployment, the data, and the URL.

​
Prerequisites

A Magic Meal Kits license

Your subscription provides a license key and an API key used by the server.

A Google account

Use the same account you sign in to Google Cloud with.

A GCP project with billing

Cloud Run requires billing enabled. MMK itself is free — infrastructure is billed by Google, and the free tier covers light usage.
Install with a personal Gmail account, not a Google Workspace account. The deployment wizard currently supports installing into the GCP environment of a regular Gmail account only. (Your Make account and the accounts you connect from Make may use Workspace freely — this restriction applies only to the Magic Meal Kits install.)

​
Deploy your server

Open make.magicmealkits.com/deploy and follow the wizard.
1

Connect Google Cloud

Click Connect to Google Cloud and grant access. Use the same Google account you use for Google Cloud so the wizard can see your projects and create resources.
2

Select the app

Choose the Magic Meal Kits template (or Magic Meal Kits Pro, depending on your plan).
3

Pick or create a project

Select an existing GCP project, or create a new one (project names are 6–30 characters, lowercase letters/numbers/hyphens, and must start with a letter). The wizard then checks billing and blocks deployment until it’s enabled — enable it in the Google Cloud Billing console and click Recheck Billing.
4

Choose a tier and deploy

Pick a resource tier, then click Let’s Go!.
TierResourcesSuited forApprox. GCP cost
Free1 vCPU / 256 MBDevelopment & testingFree within GCP limits
Basic1 vCPU / 512 MBProduction workloads~$5/month
Performance2 vCPU / 1 GBHigh-traffic production~$15/month
Magic Meal Kits is free to use. Infrastructure costs are billed directly by Google Cloud, which includes a generous free tier (vCPU-seconds, memory-seconds, and ~2M requests/month). Actual cost depends on your usage and region.
5

Done

On the success screen, use Visit Your Application to open your server, or View Deployment Status to open the App Status page.

​
What gets set up

The installer provisions everything the server needs in your project:
  • Cloud Run service magic-meal-kits (region us-west1)
  • Firestore (default) database — jobs and sync state
  • BigQuery dataset threads_data — search-heavy posts/replies storage
  • Secret Manager and Cloud Tasks
  • The required Google APIs and IAM roles, and a public (invokable) URL
It also sets these environment variables on the service:
VariablePurpose
GOOGLE_CLOUD_PROJECTYour project ID
MMK_LICENSE_KEYYour license key
MMK_API_KEYAPI key used to authenticate requests
APP_TYPEApplication type

​
After deploying

Your server URL and API key are shown on the App Status page — that’s where you copy them from (you don’t hand-configure them).

Authentication

How the X-API-KEY header and license tiers work.

Quickstart

Make your first call to your deployment.

​
Upgrading (redeploy)

To move your deployment to a newer server version, open App Status and click Update Service (Redeploy) under Service Management. The page shows your current Version and Last Deployed time. The redeploy is an in-place upgrade — it replaces the running container with the latest version and creates a new Cloud Run revision.
PreservedChanges
Server URL, API key, licenseThe container image / version
GCP project and regionA new Cloud Run revision is created
Firestore & BigQuery data—
Environment variables / config—
Redeploying does not lose data and does not change your URL or API key — only the server version moves forward. There’s no automatic “update available” banner; you trigger the upgrade from App Status when you want it.