· 7 min read

Gadget Is Winding Down. First Production Deploys End With November and the Platform Shuts Off March 31, 2027. Here Is the Migration Order for a Shopify App.

Gadget, the hosted backend a lot of indie Shopify app developers built on, published a post on November 9 titled "Gadget is winding down." New applications can't be started, effective immediately. Apps that haven't gone to production yet can do their first production deploy until the end of November. Support runs until the end of the year, and the platform stays up until March 31, 2027. If you have a Shopify app on Gadget, you have about four and a half months and no migration guide yet. That's enough time if you start with the right things.

What Gadget actually said

The announcement is short and fairly clear. Existing apps "keep running as normal" until March 31, 2027, and the team says you don't need to move anything today but should "start planning immediately." After support ends, the team says it will focus on keeping the lights on and handling critical issues.

On the reason, the post says the tools developers use to build apps are changing fast, and refers to "current financial realities." I read that as: building and maintaining a full-stack app platform got harder to fund as AI coding tools changed what developers expect from one. That's my interpretation, not Gadget's wording.

Two more details matter. Gadget says it will publish guides and tools for moving apps to other platforms "in the coming weeks" and email customers when they're ready. And it's open to someone in the community taking Gadget over in some form, through future@gadget.dev. The post doesn't name destination platforms and doesn't describe a data export process yet.

Why this one hurts more than a normal host change

Gadget wasn't just hosting. For a Shopify app it typically handled the OAuth install flow, kept a synced copy of shop data, ran webhooks and background actions, and gave you a database and API around all of it. Moving off it means replacing several pieces at once, and the Shopify-specific ones are the fiddly ones.

So when the guides arrive, I expect the database part to be the easy bit. The hard bits are the install and session flow, webhook subscriptions, and whatever logic you wrote against Gadget's synced Shopify models. Layerbase, which sells a competing database, makes the same point in its own migration write-up: a database alone doesn't replace hosting, Shopify OAuth, file storage or the sync. They have a product to sell, but on this point I agree with them.

The migration order I'd follow

This month, before November ends:

  1. If you have an app that hasn't done its first production deploy, decide now. Either ship it to production before the end of November so it runs on Gadget until March, or don't ship it on Gadget at all and build it on the destination stack instead. I'd lean toward the second option for anything you expect to sell for years, because a March cutover for a brand-new app is extra work for four months of runway.
  2. Write an inventory of every app: which shops it's installed on, which webhooks it subscribes to, which Shopify models it reads, which background jobs and schedules it runs, and which secrets and API keys it holds. This is the document every later step depends on, and you can do it today without waiting for Gadget.
  3. Export what you can now. Use whatever API or export Gadget gives you to pull your own records out on a schedule, even if it's a crude JSON dump into a bucket. Don't assume a full SQL dump will be available later.

December and January, once the guides are out:

  1. Pick the destination and stand up the install flow first. Shopify's own app templates and session storage are the obvious default, and a boring Postgres host behind them is fine. Get one test store installing and uninstalling cleanly on the new stack before you port any business logic.
  2. Move webhooks and background jobs next, then the business logic, one app at a time.

February and March:

  1. Cut over each app with a dated plan: re-point the app URL, check every merchant re-authenticates or migrates cleanly, keep Gadget running in parallel until you've seen a full billing cycle on the new stack. Aim to be done in February, not on March 30.

What I'd look for in the next host

This is the second "the platform under you is going away" notice in a week, after Val Town. The lesson I keep coming back to is that convenience platforms are fine to build on if the exit is cheap. Before I committed to the next one, I'd want three things. My data lives in a standard database I can dump myself. The Shopify integration uses Shopify's own libraries, not a proprietary wrapper. And the business logic is plain code that runs anywhere Node runs. If two of those are true, the next shutdown notice costs me a weekend instead of a quarter.

Where I could be wrong

Gadget might get taken over. The post explicitly invites it, and a community or company takeover could keep the platform alive past March. I wouldn't plan around that. If it happens, you've lost some weeks on a migration you could pause. If it doesn't, you started on time.

The migration guides could also be very good and make most of this list unnecessary. I'd still do steps 2 and 3 now, because an inventory and a data export are useful whatever the guides say.

What I'd actually do

If I had one Gadget app with paying merchants, I'd spend this weekend on the inventory and a scheduled export, and I'd install a bare Shopify app template on a test store with my chosen database behind it. That's maybe six hours, and it turns a vague March deadline into a list of concrete pieces to port. Then I'd wait for Gadget's guides before rewriting any logic, and set a personal deadline of February 15 for the first app to be fully off.

Author

Sources

Newsletter

The week, in one email.

The weekly summary of what happened and what it means for people who build alone. No spam, unsubscribe any time.

Form not showing? Subscribe on this page instead.

Related Posts