Lona gives developers a time-shaped model for events, tasks, stickers, formulas, context, and availability.
Get started1 surface for meetings, tasks, context, and availability
0 extra views to read before planning the day
Live availability from the calendar you actually use
The calendar carries the model.
Build on the same calendar your users read — events are real objects, not an opaque feed.
Time-shaped rows are the data model — query the week the way it's displayed.
Create, move, and book through the same actions the app uses, straight from your code.
Build on the surface users see.
Skip the CSV round-trip — the sheet is the live source, not an export that drifts.
What the API writes is what the user sees that instant — no separate sync layer.
Availability and booking ship with the calendar, so you don't rebuild a scheduler.
The value is a week you can read without opening every calendar event, task list, and notes tab.
| Lona | Alternative | |
|---|---|---|
| Scattered planning Your week should be readable before you make the next decision. | [yes] Calendar, tasks, context, and availability stay on one live surface | Planning stack: [partial] Calendar, tasks, notes, and scheduling often live in separate tabs |
| Real availability Booking should come from the week you actually use. | [yes] Scheduling links use the same calendar context you plan from | Scheduling tools: [partial] Booking tools often drift from the work and context around the calendar |
| Readable week A better calendar should make important days stand out. | [yes] Rows, stickers, formulas, and actions keep meaning attached to the calendar | Dashboards and to-do apps: [no] Dashboards and task lists still make you piece the week together |
| Context where the day is The why behind a day should sit on the day, not in another tab. | [yes] Notes, links, and details stay attached to the event and the row | Notes and docs apps: [no] Context lives in a separate doc or notes app you forget to reopen |
| Numbers that update themselves Your week should reflect what already happened, automatically. | [yes] Google, Garmin, Whoop, and Weather land on the calendar on their own | Trackers and widgets: [partial] Trackers make you switch apps or retype the numbers by hand |
| Ask for a view, don't build one You should describe the week you want, not configure it. | [yes] Chat assembles the rows, filters, and layout from a plain request | Filters and saved views: [no] Filters and saved views still make you piece the layout together yourself |
Start with your real calendar, then add tasks, stickers, rows, availability, formulas, and Spotlight where they help.
Preview shared weeks
Full planning surface before you pay
For calendars that need more room
For teams coordinating real availability
Save 15% with annual billing
Use rows, calendar context, and visual markers as building blocks for calendar logic.
Build on the weekRead the blog