STUDIOAbout

Small apps, built to be trusted.

AppNest Studio is an independent software studio. We build focused Shopify apps — one job each — for merchants who'd rather not find out about a problem from a customer.

Where the apps come from

WHYWhere the apps come from

Before we build anything, we read the one-star reviews of the apps already in the category. The pattern is remarkably consistent: the app is one-way when it should be two-way, it polls on a schedule so the data is stale, the core feature sits behind a paywall, and when it breaks, it breaks quietly.

So each app targets exactly that gap. Watermarkly started the studio in 2026, and the apps that follow share one engineering foundation built around real-time webhooks, logged background runs, and alerting — each one announced here when it ships.

We're small on purpose. A short queue means the person answering your email is the person who wrote the code.

What every app must satisfy

RULESWhat every app must satisfy

  1. 01

    Alert on every failure

    An app that fails silently is worse than no app. Every engine failure is persisted, emailed, and cleared with a recovery notice.

  2. 02

    Idempotent by design

    Webhooks retry. Jobs re-run. Nothing we build may double-write, double-charge, or double-tag when that happens.

  3. 03

    Server-side gates

    Plan limits are enforced on the server, before any side effect — never as a greyed-out button.

  4. 04

    Hold as little data as possible

    We store IDs and hashes, not your customers. Uninstall or a redaction request purges everything for the store in one transaction.

  5. 05

    Undo where physics allows

    Bulk operations record their reverse. If an action can't be reversed, the app says so before you run it.

  6. 06

    Truthful listings

    Feature copy describes what ships today. If it's coming, it says coming.

STACKHow it's built

Every app runs on the same foundation: Shopify's React Router app framework and Polaris components, a background job queue for anything that touches more than one record, a per-store audit log that the UI reads from, encrypted third-party tokens at rest, and health checks and error tracking in production. The foundation is shared; the apps stay separate so a bug in one can't take down another.

Browse the apps →