A booking page worth putting in your signature, and a real calendar in your browser behind it. Every meeting confirmed in both time zones from one instant, checked against your live calendar at the second somebody presses confirm.
Free today, including the calendar. No card, no trial clock, no sales call.
Every competitor price on this page was read off that company's own pricing page, dated and linked. The full inventory is at /capabilities, and machine-readable at /capabilities.json.
The time that was not the time. Somebody in London books your 10 o'clock and arrives at five in the morning your time, or worse, nobody arrives at all and each of you privately decides the other one is unreliable. Nearly every scheduling tool converts a time and shows you the answer. The failure is not the arithmetic, it is that the two of you were never shown the same fact at the same moment, in both of your languages, and asked to confirm it.
The slot that was already gone. Your page offers 11 o'clock because it last heard from your calendar four minutes ago and a change notification went missing in between. Somebody takes it. Now you are the person emailing an apology about a meeting your own software sold twice.
The link that looks like everybody else's. You are an advisor, a partner, a consultant, a private banker. Your entire proposition is judgment and taste, and the object you send most often is a generic booking page carrying a stranger's logo you cannot remove. It is a small thing and it is read every single time.
The calendar you do not actually control. The scheduling tool holds your booking page. A separate calendar app holds your day. Nothing at all holds the rules you keep in your head about when you will and will not meet, so you enforce those by hand, every week. Owning one half of the loop is what stops the other tools from closing it.
Cachet Calendar is built around those four, in that order.
Sign in and grant three scopes: read your free and busy times, list which calendars you have, and write the events you create. Nothing else is requested. It takes under a minute and it is the only connection you make.
Weekly hours, meeting types with their own length and buffer, the questions you want answered before somebody books, and standing instructions in plain English. Your calendar starts enforcing the rules you already keep in your head.
They pick a time, see it confirmed in both zones, and answer your questions. A real event lands on both calendars with a Google Meet link, and they keep a private link to move or cancel it without emailing you.
What happens at the moment of confirm. Your free and busy times are polled live from Google, not read from a cached mirror. The standing rules are applied a second time, so a slot that a rule protects cannot be taken by somebody who kept an old link open. A meeting type longer than your own duration cap never appears in the first place. Then the event is created with both parties as attendees, and Google itself sends the invitation, so it lands in the inbox looking like a meeting instead of like marketing.
Booking tools sell you a page and send you back to somebody else's calendar app. Calendar apps sell you a beautiful client and bolt a thin booking page onto the side. Cachet Calendar runs both, which is what lets a rule you said once be enforced at the moment somebody books.
Agenda, day, week, month, quarter, and year, at /calendar with your real Google calendars, each one in its own color, shown or hidden as you like, and the choice is remembered. On the free tier, with no upgrade prompt attached to it.
A drag writes only the times. It never overwrites the description, the attendees or the color, which is the quiet bug that makes people stop trusting a third-party calendar.
Standard recurrence rules (daily, weekly, every two weeks, monthly, yearly), described back in plain English with the next dates previewed before you save. Recurrence is generated in the event's own zone, so a nine o'clock weekly meeting is still nine o'clock in November.
Each calendar is mirrored using Google's own incremental sync tokens, re-baselined automatically when a token expires, and the interface states when it last synced and which calendar failed if one did, so you always know the view in front of you is current.
A language model reads the phrase, and it holds to two rules: it keeps your title intact, and when a phrase is vague, such as "in the evening", it asks instead of quietly inventing a time. If the model is unavailable a simple pattern reader takes over and the interface says so.
The calendar is a browser tab, so it opens on a Mac, a Windows machine, an iPhone and an Android phone with nothing to install, nothing to update, and no store in the way. Native clients ride the same sync layer when they land.
"Keep Friday afternoons clear." "No meetings before nine." "Nothing after six on weekdays." "Keep meetings under 90 minutes." You say it in plain English, it is restated back to you in plain words so you can see it was understood correctly, and from then on it is enforced. There are two halves, and they behave differently on purpose.
A protected window becomes real busy time on your booking page, so nobody can book into it. A meeting type longer than your cap is not offered. This is enforced where slots are displayed and again where a booking is confirmed, so somebody holding an old link cannot walk through it. No message is sent to anybody to make this true. It is simply not available.
Meetings already on your calendar that break a rule are listed for you to handle. Cachet Calendar does not decline them and does not write to the organizer. Declining somebody else's meeting carries your name, and it stays your decision, every time.
Why nobody else does the first half. Preventing a booking requires owning the booking surface. Reading your rules requires owning the calendar. Of the 11 alternatives compared below, none enforces a rule you said once at the moment of confirm on its own booking surface: read the "Rules you say once" column below and not one of the 11 answers Yes. The two that come closest, Motion and Reclaim, schedule around your habits instead of enforcing a rule you stated, so their equivalents can only advise you after the fact. Outside this comparison set, Microsoft Copilot's calendar instructions come nearest, and they need a Microsoft 365 seat.
Cachet Coordinate helps groups agree on a single block of time, whether for a four-hour retreat, a board afternoon, or a family dinner. The organizer drags proposed slots onto a calendar, sends personal invite links, and watches votes come in live. Deciding books a real Google Calendar event for everyone, with the Meet link, sent by Google itself. The people you invite pay nothing, ever.
Paste an iCal link from Trip Underway, TripIt, or any travel calendar once, and travel days block themselves alongside Google Calendar busy time, so nobody's flight day ends up as the group's winning block.
Calendly limits group polls to a binary thumbs-up, but real decisions depend on flexibility. Guests vote with Works, If needed, or Can't, with each vote attributed by name and face. You see everyone's stated intent immediately instead of forcing people into a strict yes or no.
Every proposed time has its own comment thread. Instead of sorting through side chats or separate email chains, your group leaves notes on specific slots. Questions and adjustments stay tied to the block being discussed.
Identity and privacy, both by design. Every participant is a named, verified invitee, so a vote carries a face and cannot be overwritten by somebody retyping the same name. Busy time works the opposite way from votes: it appears only as counts, enforced server-side, so nobody ever sees whose calendar blocks a slot, only how many people are free.
A calendar and a booking page in one product, on the free tier, with every capability below working today. What comes after it is set out at the end, so you can see the direction as well as the product.
At /b/ plus your handle. The invitee books with no account at all.
Polled from Google at the moment of booking, not read from a mirror that may be stale.
Both times formatted from one moment in Coordinated Universal Time, so they always refer to the same moment.
A real event on both calendars, with a meeting link, sent by Google itself.
A private link on every booking. No login, no email to you, no negotiation.
Name, length and buffer per type; your own hours per weekday.
Defined per meeting type, required or optional. A missing required answer is refused before any event is created, and every answer reaches your confirmation email and the event itself.
Upcoming soonest first, past most recent first, with the guest, the type and the time in your own zone. A canceled booking stays visible with a label rather than vanishing.
Time-of-day windows and duration caps, in plain English, enforced on the booking page.
Members respond in the view that suits them best: a welcome letter, a best-times list, a week calendar, or a full grid.
Scheduling is one product with a long arc. None of what follows changes what the free tier does today.
The person booking sees their own conflicts laid over your page, so the time you agree is a time that works on both calendars.
Outlook, iCloud, and Fastmail join the Google connection, so the calendar you already live in is the one it reads.
An assistant that negotiates a time with the other side's assistant, over the Model Context Protocol, and hands you the result.
Booking at your own address, deposits taken at the moment of booking, and one shared page for a whole firm.
These are the moments Cachet Calendar was built around.
Half your meetings cross an ocean and the other half cross three states. When you send a time, both of you see both zones, agreed on screen before anybody commits. Timezone confusion stops being your problem to police.
It sits in your signature and goes out more often than your website does. It should look like it belongs to somebody whose judgment is worth paying for, not like a form.
You have rules. You enforce them by hand, which means you enforce them until the week gets busy. Said once here, the rule becomes busy time nobody can book into, and it holds on the weeks you are not watching.
The reservation number, the account, the one question that decides whether the meeting is 20 minutes or an hour. Ask it on the booking page as a required answer, and it arrives in your confirmation and on the calendar event.
A borrowed laptop, a hotel machine, a Windows desktop at a client office. The calendar is a browser tab. There is nothing to install and nothing to sign into twice.
They have a private link on their own confirmation. They move it themselves, your calendar updates, and neither of you writes an email that begins with "so sorry to do this".
Every published price below was read off that company's own pricing page on 27 July 2026 and the company name links to it. Prices move, so check the current figure before you rely on one. One of them, YouCanBookMe, publishes no figure on a page that can be read without running its application.
| Product | Entry price | Free tier | Full calendar client | Rules you say once |
|---|---|---|---|---|
| Cachet Calendar | Free todaypaid plans published below | Yes: one booking link, the full calendar, standing instructions | Yes, in the browser | Yes, and enforced on the booking page |
| Calendly | Free, then $10 per seat per monthbilled yearly; Teams $16, Enterprise from $15,000 a year | Yes, one event type | No | No |
| SavvyCal | $10 per user per monthPremium $17; no free plan, 30-day money back | No | No | No |
| Cal.com | Free for one userTeams $12 per user per month, Organizations $28 | Yes, generous | No | No |
| Vimcal | $20 per month$16.67 billed annually; free tier is iOS only; Vimcal EA $75 | iOS only | Yes | No |
| Motion | $19 per seat per monthabout $12.73 billed annually; Business $29 | Trial only | Yes | Auto-scheduling, not stated rules |
| Reclaim | Free (Lite)Starter $10, Business $15, Enterprise $22 per seat per month | Yes, one user | No | Habits and focus-time defense |
| Acuity Scheduling | $20 per month$16 annually; Standard $34, Premium $61; no free plan | No | No | No |
| Doodle | FreePro $11 a month billed annually; Team $9 a seat | Yes | No | No |
| TidyCal | $29 once, for lifeAgency lifetime $79; Pro $12 a month | Yes | No | No |
| Fantastical | Free, then $6.99 a monthor $56.99 a year; Premium for Families $89.99 a year (prices as listed by Apple for Flexibits' own subscription, 2026-07-27) | Yes, basic calendar | Yes, native | No |
| YouCanBookMe | Free plan; paid not publishedthe pricing page shows plan names and asks you to contact sales for the figure (checked 2026-07-27) | Yes, one page | No | No |
Every published price above is linked to the page it came from, so you can check each one. Cachet Calendar is built for the case where the meeting itself matters more than the tooling around it: the time is right in both zones, the slot is genuinely free, and the rules you keep in your head are enforced by the page rather than by you.
What is requested. Three Google scopes: your free and busy times, the list of your calendars, and the ability to create and update events. Not your mail, not your contacts, not your files. You can see exactly what was granted in your Google account at any time, and disconnect there or here.
What we hold. An access token held server-side, your own settings (hours, meeting types, questions, rules), and a record of the bookings made through your page. The token never leaves the server that uses it. Calendar contents are read when a page needs them and are not warehoused.
What is never done. Your calendar is never sold, never used to train a model, never shared with another account, and never used to advertise to you. There is no data broker in this product and there is no plan to introduce one. A public booking page is resolved by a single lookup that constrains both the handle and its one owner, and the pointer and the record have to agree before anything renders, which is what keeps one account's page from rendering another's.
Analytics. This site measures page views and which sections people read, through PostHog, and nothing is captured until you accept. Inputs and text are masked, do-not-track is respected, and the product's own counters are aggregate totals with no personal information in them at all.
Email. Confirmations are sent by Google as real calendar invitations, from the account you connected. Cachet Calendar sends you a confirmation of your own with the answers to your questions. Nothing is ever emailed to the person booking you beyond what the booking itself requires.
Every figure is below, in public, with no form in front of it. Nothing here asks for a card. The calendar client, one booking link, standing instructions and answering any group coordination are free right now; the Signature tier below carries the additions. A paid plan never takes away anything you have already set up.
Why these numbers. The premium end of this category is Vimcal at $20 a month, or $16.67 billed annually, and Acuity Premium at $61. The volume end is Calendly and SavvyCal at $10. Cachet Calendar is priced against the premium end because it carries a calendar client, a booking page, and organizer-side group coordination in one tier, and then discounted hard for paying annually. The people you invite to a coordination pay nothing, ever: charging your guests to answer you would be a strange way to say thank you. Cal, the scheduling agent that negotiates on your behalf, arrives with the Cachet suite's Concierge tier and is priced with the suite, not here. Annual billing is what funds live sync and the language model behind natural-language entry, which is why the tiers above are subscriptions: a one-time price sold against an unbounded recurring cost is a promise that eventually gets broken.
Canceling. One click, always visible, no mandatory explanation and no retention maze. One pause offer, and then you are let go. It is written down here so it cannot quietly become something else later.
No. They open your link, pick a time, type a name and an email, and they are done. There is no sign-up wall, no app to install, and no password. The only account in the whole flow is yours.
Google Calendar today, and the connection is complete: multiple calendars, incremental sync, and live free-busy at the moment someone books. Microsoft 365 and CalDAV, which covers Outlook, iCloud, and Fastmail, are in build now and are the next connection to land.
Your free and busy times are read live from Google at the moment somebody is looking at your page, and read again at the moment they press confirm, so a slot that filled while the page sat open is caught. Most tools rely on a change notification arriving from the calendar provider, and that message is the first thing to go missing when a calendar is busy. Reading at the moment of truth costs a fraction of a second and catches the case a notification would have lost.
Every time on every surface is printed twice, once in your zone and once in theirs, and both are formatted from the same single moment in Coordinated Universal Time. Both labels come from the same instant, so they always refer to the same moment: a different and stronger position than converting a time and hoping.
Both, and that is the unusual part. You get a full calendar in your browser with six views over your real Google calendars, agenda through year, and you get a public booking page, in one product, on the free tier. Almost every rival sells you one half or the other.
A scheduling rule you say once in plain English, such as keep Friday afternoons clear, or nothing after six on weekdays, or keep meetings under 90 minutes. It is restated back to you in plain words so you can check it was understood, and then it keeps applying. Half of it prevents (the protected window becomes real busy time on your booking page), and half of it surfaces (meetings already on your calendar that break a rule get listed for you to handle).
Never. Declining somebody else's meeting is an outward act with your name on it, and that stays your decision. Cachet Calendar shows you the conflicts and stops there. It sends no message to anyone on your behalf.
Nothing today. The calendar client, your booking link, standing instructions, and answering any group coordination are all free right now. Organizing your own group coordinations sits in the Signature tier, and the paid tiers are published in full in the pricing section above, so you can judge them before you invest any time.
The calendar client runs in a browser, so it opens on a Mac, a Windows machine, an iPhone, and an Android phone, and it is the same client with the same data on each of them. Native apps ride the same sync layer when they land.
It stays between you, Google, and the server that books for you. Cachet Calendar holds an access token server-side, reads what you granted, and writes the events you create. Your calendar content is never sold, never used to train a model, and never shown to another account. The privacy section above sets out exactly what is held, and what is never done with it.
Every part of the product, with what is live now and what is being built behind it.
The connection is Google Calendar, and it is complete: multiple calendars, incremental sync, live free-busy at the moment someone books. Microsoft 365 and CalDAV, which covers Outlook, iCloud, and Fastmail, are in build now and are the next connection to land.
The calendar runs in the browser, so the same client opens on a Mac, a PC, a phone and a tablet with nothing to install and nothing to update. Native apps are on the roadmap for the places a browser cannot reach.
A calendar and a booking page, aimed at the moment two people agree on a time. Group coordinations already block whole travel days from an iCal feed; per-meeting transit time, which shortens what a stranger can book around a trip across town, is the next thing to land, because it changes what can be booked and not only what is displayed.
Per-calendar visibility is yours to set and it is remembered between visits. Sets that switch themselves by time of day or by location are on the roadmap.
Standing instructions understand windows of the day and duration caps, and they are enforced at the booking surface rather than merely displayed. Attendee-aware and topic-aware rules are next, and no rule ever declines a meeting already on your calendar.
Taking a deposit at the moment of booking, one shared page for a whole firm, and booking at your own address. All three are designed, queued and in the build order above.
Cachet Calendar is one of four. They share a mark, a color band and an account, and each one handles a different part of the same job: being someone worth meeting, and then actually meeting them. The whole family, and what each one costs, is at cachetcomplete.com.
The digital card you hand over. It opens like a title sequence and saves like a handshake. cachetcard.com
Everyone you met, remembered properly, with the context of where and why.
The follow-up that decides whether the introduction turns into anything.
This one. The meeting itself, at a time that is right in both zones. cachetcalendar.com
Sign in, connect Google, set your hours. The first booking link works in about two minutes and costs nothing. If you would rather look before you touch anything, the demo page is real and open: open a real booking page.
Open a real booking page and watch both time zones agree. It takes about 15 seconds and asks nothing of you.
Open a real booking page