For SaaS
Put your product in your customers’ menu bar.
One JSON file makes your SaaS TailApps ready. Your customers get a live status in their menu bar, a card on their Dashboard, and with a push URL, a card and alerts on their iPhone. You don’t build a Mac or iPhone app.
What your customers get
Your product, where they already look.
One card shows up everywhere TailApps does. It’s drawn natively from TailApps’ own parts, so it looks right on every surface and you maintain one file.
-
Menu bar
A live label like “7 open” or “£1,240 today”, coloured when something needs a look.
-
Cards and pop-outs
Open it from the menu, pop it out as a floating window, or pin it to the Dashboard next to their other cards.
-
iPhone
Add a push URL and the same card shows up on their iPhone, with a notification when you send an alert.
-
Their agent
Customers can ask Claude to change it (“show only bugs”, “add a chart”), and TailApps asks before anything new is allowed.
How it works
Three steps. Your existing API does the work.
Say you run Acme, an issue tracker. Your customers want their open issues in the menu bar. You already have an API and API keys, so that’s all you need.
-
Step 1
Describe the card in one JSON file
Say what to fetch, how often, and how to show it. This card is data, not code: TailApps draws it with its own native parts and runs only steps built into TailApps.
Your endpoint returns plain JSON, for example:
{ "open": 7, "done": 12, "issues": [ { "title": "Fix login redirect", "state": "blocked" }, { "title": "Export to CSV", "state": "in progress" } ] }Step 2
Your customer adds their API key, once
"auth": "acme" names a connection, never a key. When a customer adds the card, TailApps shows what it may do (“Connect to api.acme.dev”) and asks for their Acme API key. The key goes into their Keychain, is sent only to your API, and never appears in the card, its logs or its data.
Have OAuth? Skip the key. Add an "oauth" block and use "auth": "oauth:acme", and customers tap Sign in with Acme in the system’s own sign-in sheet, on the Mac and the iPhone. It works with any provider that supports PKCE without a client secret, like Linear, and the token only goes to the hosts you list.
Step 3
Publish it in the Directory
Upload the file to the Directory. Each version is reviewed and, once approved, signed, so customers see “Verified”. Link to its page from your settings or docs: Open in TailApps installs it on their Mac, and their iPhone gets it from the Mac.
Or let Claude write it
With TailApps connected to Claude Code, one sentence is enough. It writes the JSON, checks it and installs it for you to approve:
“Build a TailApps card that shows my open Acme issues in the menu bar, using the API at api.acme.dev/v1/me/issues.”
-
acme-issues.json
{ "schema": "tailapps/v0", "app": "acme-issues", "name": "Acme Issues", "description": "Your open Acme issues, in the menu bar.", "icon": "checklist", "version": 1, "permissions": ["net:api.acme.dev", "open:url"], "state": { "mine": { "type": "object", "default": { "open": 0, "done": 0, "issues": [] } } }, "sources": { "mine": { "fetch": "https://api.acme.dev/v1/me/issues", "auth": "acme", "every": 120 } }, "cards": [{ "id": "main", "layout": { "column": [ { "row": [ { "stat": "$mine.open | number", "label": "Open", "grow": true }, { "stat": "$mine.done | number", "label": "Done this cycle", "grow": true } ] }, { "list": "$mine.issues", "limit": 5, "empty": "Nothing assigned to you", "item": { "row": [ { "text": "$item.title | truncate:40", "grow": true }, { "badge": "$item.state", "tone": "$item.state | tone:{done:'good', blocked:'bad', else:'accent'}" } ], "align": "center", "gap": "s" } }, { "button": "Open Acme", "on": "open_acme", "style": "plain" } ], "gap": "m" } }], "actions": { "open_acme": { "steps": [{ "open": "https://acme.dev/my-issues" }] } }, "views": { "menubar": { "icon": "checklist", "card": "main", "in_menu": "row", "label": "{$mine.open} open" } } }
Optional: real time
Want it instant? Push to it.
Fetching every couple of minutes is fine for most cards. For “a new issue was assigned to you” the moment it happens, add a push URL. It works like the Slack webhook field you probably already have.
-
1
Swap the fetch for an inbox
Same file, same cards, and no API key on the customer’s side. Listing iOS lets pushes reach their iPhone too, even while the Mac sleeps, once they turn on Sync to My Devices for the card there.
-
2
Your customer pastes their push URL into your settings
Each customer gets their own private URL in TailApps (Get a Public URL, set to All My Devices), and can turn on a signing secret on their Devices page at tailapps.com. You store both, like any webhook.
-
3
POST JSON when something changes
Each push replaces the last, so send the whole picture: up to 64 KB, 10 pushes a second per URL. Add an X-TailApps-Alert header and the iPhone shows a notification. Sign the body with a timestamp, a new nonce and an HMAC, and nobody else can send or replay one. The alert line isn’t part of the signature, so keep secrets out of it.
In acme-issues.json
"permissions": ["inbox:mine", "open:url"],
"sources": {
"mine": { "inbox": "mine", "platforms": ["macos", "ios"] }
}
From your Laravel app
use Illuminate\Support\Facades\Http;
use Illuminate\Support\Str;
// $user->tailapps_url: the push URL your customer pasted in their settings
// $user->tailapps_secret: its signing secret (optional, but recommended)
$body = json_encode(['open' => 7, 'done' => 12, 'issues' => $issues]);
$timestamp = time();
$nonce = Str::random(32);
Http::withHeaders([
'X-TailApps-Timestamp' => $timestamp,
'X-TailApps-Nonce' => $nonce,
'X-TailApps-Signature' => 'sha256='.hash_hmac('sha256', "{$timestamp}.{$nonce}.{$body}", $user->tailapps_secret),
'X-TailApps-Alert' => 'New issue assigned to you: Fix login redirect',
])->withBody($body, 'application/json')->post($user->tailapps_url);
Or anything that can make a request (to a URL without a signing secret)
curl -X POST "$PUSH_URL" \
-H 'Content-Type: application/json' \
-H 'X-TailApps-Alert: New issue assigned to you' \
-d '{"open": 8, "done": 12, "issues": [{"title": "Fix login redirect", "state": "blocked"}]}'
Good to know
What works where, today.
- API keys live on the Mac, sign-ins work everywhere
- The iPhone can’t hold API keys yet, so a card that fetches your API with a key runs on the Mac, and the iPhone shows it as a preview. An OAuth sign-in works on both, so the phone can fetch your API by itself. Or use a push URL, or have the Mac’s copy send what it fetched to the phone.
- Your customers stay in charge
- Every capability is shown in plain words and approved once. An update that asks for more asks again. Nothing runs that the customer hasn’t approved.
- Privacy of pushes
- Messages between a customer’s own devices are end-to-end encrypted. A push from your server is protected by HTTPS and a signature, not end-to-end encryption, and tailapps.com sees it. A URL set to All My Devices keeps the last 20 pushes for up to 30 days, so new devices catch up; one set to This Mac keeps only the latest.
- Pricing
- Everything is free during the beta. Later, the Mac app stays free on its own, and hosted push URLs and syncing to other devices become part of Pro.
Everything a card can do, by platform: Capabilities · More on approvals, keys and signing: Security · Examples
Coming soon
Even less to do.
Not here yet. These are next for SaaS teams.
-
Coming soon
Push helpers
A one-line TailApps::push() for Laravel, and a package for Node, with signing built in.
-
Coming soon
Sign-ins that need a secret
GitHub OAuth apps, Notion, Slack and other providers that need a client secret, with the secret kept on tailapps.com.
-
Coming soon
API keys on iPhone
Paste an API key on the phone too. OAuth sign-in already works there.
Want your product in TailApps at launch? Tell us about it
Your cards, built by your agent.
Free during the beta. Start on your Mac, add your iPhone, and script it all from the terminal.
- Mac
- iPhone Beta
- CLI
- Windows Soon
- Linux Soon
- Android Soon
Then connect your agent:
claude mcp add tailapps -- /Applications/TailApps.app/Contents/MacOS/tailapps-mcp