Get started
Overview
What Packlets does, when to use a channel and when an app, and how these docs are organized.
Packlets isn't public yet. You'll get a key at launch through the waitlist.
Packlets brings software you built yourself to your phone. Your tool sends a message with a single HTTP call, and Packlets shows it as a push. And what you tap, toggle or write in the app arrives back at your tool.
Your code keeps running on your side: on your computer, a server, a Raspberry Pi or as a cron job. Packlets is just the way to your phone and back.
Channel or app
Every tool you connect gets its own place in the app. When connecting, you choose what your tool should do: Messages (a channel) or Your own app (an app). In a channel you can also Allow replies, and then you write with your tool like in a chat. You can flip this switch at any time.

Server
Today, 9:41
Daily report
- 3 deploys, all successful
- Backup finished at 3:00
api.example.com is not responding
No health check since 9:38 AM. Last status: 502.

Assistant
Today, 9:41
How many orders did we get yesterday?
Yesterday brought 23 orders, 4 more than average. 2 haven't shipped yet.
Which ones?
- #1042, Lena K., open for 2 days
- #1047, Jonas M., waiting for stock
Account
| In the app | Use it when … | Examples |
|---|---|---|
| Messages (channel) | your tool reports something on its own. | Server goes down, deploy or backup fails, new order, daily report |
| … with Allow replies | you want to tell your tool something or ask it something. | your own AI agent, bot with commands |
| Your own app (app) | you want to check or work through something again and again. | approving invoices, server dashboard, reviewing pull requests, support inbox |
Not sure? Start with a channel. It needs just one HTTP call. An app is a web page that you build yourself and run on your own server.
If your tool can already send to Slack, Discord or ntfy, it works entirely without code: when connecting, tap Integrations and choose Slack, Discord or ntfy. That way, for example, your uptime monitor reports in Packlets.
How the docs are organized
Read from top to bottom. Each part builds only on the parts before it.
| Part | What you'll find there |
|---|---|
| Getting started | Quick start: your first message in five minutes. Then How Packlets works with all the terms. |
| Channel | Send messages, buttons and elements in them, templates, several services in one channel, push and quiet hours. |
| Reacting to input | The webhook: how your tool learns what you do in the app. Buttons, elements and replies build on it. |
| Replies | Build a chat bot. |
| Apps | Build your own app: your web page as an app in Packlets, with notifications behind the bell. |
| Reference | For looking things up: every call, every element, every event, every error. |
| Help | Troubleshooting, ready-made code and security. |
Prefer to have your coding assistant build it? Then Build with AI is all you need.
Cost
The app, push notifications, buttons, chats and your own apps are free.