Skip to content

For indie developers and small app teams

Everything after
the code ships

Waitlists, releases, support and performance for your apps, in one console. For teams shipping on iOS, Android, macOS, Windows, Linux and the web.

Open the console

The first member of every team is free

One build, six platforms

  • iOS
  • Android
  • macOS
  • Windows
  • Linux
  • Web
The Publishable console showing the Tidepool project's support inbox: open tickets with their message, sender, platform, app version and Jev's tags such as Crash, Bug, Feature request, Performance and Security.
The support inbox in the console, as it looks today.

Features

Every part of shipping, in one console

A project turns on only the features it uses. These are the screens you work in, exactly as the console draws them.

Releases

One build, a status for every platform

Each release lists where it stands on every platform: released, ready, in review, building, failed or changes requested. Send out the ready builds when you choose.

Tidepool's releases, newest first. 2.4.0, build 431: Ready on Web, Building on iOS and Android. 2.3.1, build 424: Released on iOS and Android, Ready on Web, In review on macOS, Building on Windows, Failed on Linux. 2.3.0 released on all six platforms. 2.2.4 with Changes requested on macOS.

Waitlists

Know who is waiting

Your app joins a list by its ID. Search, add, export and remove people, and joining twice answers the same.

A fact worth knowing

Joining twice answers the same.

So the public key inside your app can't be used to find out who is on a list.

  • Search
  • Add
  • Remove
  • Export as CSV

Support

Tickets arrive already tagged

Jev, TypeSafe's decision model, tags each ticket. Filter open or closed tickets by tag, or search them.

The nine tags Jev can give

  • Crash
  • Bug
  • Performance
  • Compatibility
  • Design
  • User experience
  • Feature request
  • Content
  • Security

A ticket can carry several. Each one keeps its message, and the email, platform and app version when people send them.

Supervise

See how fast your apps start

Your apps send their launch and screen timings, their own events and errors. Open any session to see what happened, in order.

What it measures

  • Cold launch
  • Warm launch
  • First render
  • Interactive
  • Screen render
  • Update download
  • Warnings
  • Errors

The median, p90 and p99 of each, by release, platform and environment. Kept for 90 days.

Teams and access

Decide who does what

Access policies grant project permissions to people and groups. Members can come through SSO and SCIM.

Per project, you can grant

  • View or manage waitlists
  • View or manage releases
  • View or manage support
  • View Supervise or delete its data
  • Manage or delete the project

People on your verified domain join at once. Sessions are listed per device, and the activity log shows who did what, API keys and AI apps included.

AI assistants

Your assistant works as you, within your limits

Add the MCP server to an assistant and sign in. You choose read only or read and change, and the teams it works in. Connected apps stay listed in your account, where you can disconnect them.

The consent page: Allow Field Agent to use Publishable as you? fieldagent.dev, verified. What it can do: Read only, or Read and change, which is selected. Teams: Lumen Labs ticked, Northwind Studio not. Deny and Allow.

API

Keys that hold only what you give them

Secret keys for your servers, CI and scripts, each with only the permissions you give it. The reference covers every route, field and error, as OpenAPI.

From your server, CI or scripts

Authorization: Bearer psk_…

# A project API key, holding
# only what it was given.
API reference

Calls to the public API are not charged.

Code is half
the app.
Publishable runs
the other half.

How it works

From an empty project to your first sign up

  1. 01 Create a projectGive each app its own project and icon, then turn on only what it uses: waitlists, releases, support, Supervise.
  2. 02 Connect your appApps and web forms call the client API with the project's public key. A sign up or an update check is one request.
  3. 03 Run it from anywhereWork in the console, from CI with a project API key, or through your assistant over MCP.
POST https://client-api.publishable.app
  /v1/waitlists/wl_pro/entries

X-Publishable-Key: pk_live_4Tq8nRw2ZsK7vYc1
Content-Type: application/json

{ "email": "joao.ferreira@sapo.pt" }

# Joining twice gets the same answer,
# so the public key reveals nothing.

Downloads from update offers are counted per release.

Pricing

Prepaid, and the first member is free

Your team tops up a balance in US dollars through Stripe, from $5. You pay for people beyond the first and for what your apps send through the client API.

Members

First member of every teamFree
Each other member$20a monthor$200a yearYour team picks monthly or yearly.

Client API usage

  • Waitlist entriesNot charged yet
  • Support ticketsNot charged yet
  • Release downloadsNot charged yet
  • Supervise eventsNot charged yet

Each will be priced per unit. Until then the console counts them and charges nothing.

Never charged

  • Calls to the public API from your servers, CI and scripts
  • Everything your assistant does over MCP
Open the console

FAQ

Questions, answered

Still curious? The API reference covers every call.

Who is Publishable for?

Indie developers and small app teams shipping on iOS, Android, macOS, Windows, Linux and the web. It keeps everything around an app after the code: who is waiting for it, which build is out where, how fast it runs, and what people say about it.

Does Publishable build my app?

No. Your CI builds it and reports building or failed for each platform. The store review reports in review, changes requested, ready or unavailable, and you release what is ready from Publishable.

Can someone use my public key to see who is on a waitlist?

No. Joining a list twice gets the same answer as joining once, so the public key in your app cannot reveal whether an email is already on it. In the console you can search, add, remove and export a list as CSV.

What happens when a store pulls a build?

Publishable takes it back for that platform automatically. You can also withdraw a platform yourself, from the release's page.

How does my app know an update is out?

It asks the client API for the latest release on its platform and gets the newest released build: version, build, notes and a download link. Downloads are counted per release.

What does Supervise measure?

How fast your app starts on real devices: cold and warm launch, first render and when it is ready for input, how fast each screen renders, and how long an update takes to download. Your app can also send its own events, warnings and errors. Each comes with its release, platform and environment, and any session can be opened to see what happened, in order. Data is kept for 90 days.

How does an AI assistant connect?

Point it at the MCP server at api.publishable.app/mcp and sign in with your account. You pick its teams and whether it may only read or also change things. It then acts as you, with only what you may do. It is listed with your connected apps, where you can disconnect it, and what it does lands in the activity log.

What does it cost?

Your team tops up a prepaid balance in US dollars through Stripe, from $5. The first member of every team is free; each other member is $20 a month or $200 a year. Client API usage (waitlist entries, support tickets, release downloads and Supervise events) will be priced per unit. The public API and MCP are not charged.

Where do I use it?

In the console on the web at console.publishable.app. The console also comes as an app for iPhone, iPad and Mac.

Ship the build.
Run the rest here.

Waitlists, releases, support and performance for every app your team makes, in one console.

Open the console