One product.
Every surface.
Honeycake is one thing: the .cake, a file that carries its own encryption, permissions, and audit trail wherever it goes. You can Bake and Open cakes from a dozen places. Every surface Opens every .cake. What each surface can Bake differs, and this page tells you exactly what.
What each surface can do
Open is universal. Layer Bake and Parbake need a desktop or the CLI. Automation lives in the CLI.
| Surface | Open any .cake | Bake any file | Layer Bake per-section readers |
Parbake redacted .cake.pdf |
Ingredients searchable label |
Automation scripts, CI, folders |
|---|---|---|---|---|---|---|
| macOS and Windows app | ✓ | ✓ | ✓ | ✓ | ✓ | – |
| iOS and Android app | ✓ | ✓ | – | – | – | – |
| Web: Portal and Opener | ✓ | ✓ | – | – | – | – |
| Gmail extension | ✓in browser | ✓attachments | – | – | – | – |
| Outlook add-in | ✓in browser | ✓attachments | – | – | – | – |
| CLI | ✓ | ✓ | ✓csv, json, xlsx, pdf | ✓ | ✓ | ✓ |
Roll your own. Every surface above is a client of the same API, which registers cakes, answers permission checks, and delivers keys. Build a surface of your own on it: a report pipeline, an internal tool, a feature inside your product. Your code Bakes and Opens on your machines, with the same keys and audit trail as ours.
Managing a cake after you send it (add a reader, rescind one person, extend its life, or Burn it for everyone) happens in the Portal, from any device. The Uploader is for the people sending to you: they Bake into your storage with nothing installed.
Where you Bake and Open
Desktop
macOS and Windows. Bake, Open, and manage cakes locally, plus the desktop-only superpowers: Layer Bake™, Parbake™, and Ingredients.
Download →Mobile
iOS and Android. Bake any file straight from the share sheet and Open any .cake with a tap.
Download →Web: Portal and Opener
The Portal is where you Bake in the browser and control every cake you have sent. The Opener is for recipients: nothing to install, Open in the browser, free.
Learn more →A Bake button inside Gmail and Outlook. Send a .cake straight from your inbox; recipients are keyed by address and Open in the browser.
Learn more →Automation, and what runs underneath
CLI
The automation surface. Bake inside scripts, CI pipelines, and cron jobs, headless, with the same keys and audit trail. Layers, boxed parbakes, groups, JSON output.
Learn more →API
Roll your own surface. The API is what every surface on this page runs on: it registers cakes, answers permission checks, and delivers keys. Build your own client on it and your code does the Baking and Opening, on your machines, with the same keys and audit trail as ours.
Learn more →Vault, via the CLI
Point the CLI at a folder and everything dropped in is Baked automatically with your rules.
Learn more →Uploader
Inbound collection. Vendors, clients, and families drop files into your branded page; they land Baked in your own storage.
Learn more →Superpowers
Redaction
One source of truth, many views. Send a single .cake to ten readers; each sees only the sections they are cleared for. Layer Bake™ and Parbake™, on desktop and the CLI.
Learn more →Ingredients
The label, never the document. Give every sealed file a searchable cover your DMS indexes and your AI can read. The document underneath stays encrypted.
Learn more →See it on a real job
HR spreadsheets, board decks, secrets in git, student records. Step by step, with what each reader ends up seeing.
Browse the Recipes