About
Scheduling, without the markup.
Neos Meet is a booking-link tool for individuals and teams. You publish a link, invitees pick a time that is genuinely free on your calendar, and a real calendar invite with a video link lands in both inboxes. That is the whole product — and it is priced like it.
Why we built it
Scheduling is a solved problem that is still sold like an enterprise platform: per-seat pricing that escalates on renewal, reminders locked behind a paid tier, round-robin locked behind the tier above that. We wanted the same daily job done for a fraction of the cost, with the parts a small team actually uses — team booking links, reminders, and calendar conflict checking — available without a procurement cycle. The pricing page and the side-by-side comparison show exactly where the difference comes from, sourced and dated.
How we operate
Signing in gives us your name, email, and profile photo — identity only, never your calendar. Connecting a calendar is a separate, skippable step, and it asks for two calendar permissions. Free/busy returns busy time ranges and cannot return event titles, guests, or descriptions — that limit is Google's, not ours. The second is read/write over the events you organize, so a booking becomes a real invite; Google publishes nothing narrower, so it also permits reading events we never touch. We don't, but that is a limit we keep rather than one the API enforces. We say which is which because the difference is the whole point.
The security page lists what we don't have — no SOC 2, no HIPAA/BAA, no SSO or audit logs yet — next to what we do. A trust page that only lists wins is the one buyers stop believing.
Prices, plan limits, and every competitor figure quoted on this site come from a single file in the codebase with a dated freshness stamp. If you find a stale number, telling us is doing us a favour.
Outlook and Microsoft 365, auto-created Zoom and Teams meetings, SMS, workflows, and CRM integrations are roadmap, not features — labelled that way everywhere they appear, and dated on the public roadmap. (Pasting your own Zoom link onto an event type works today — that's the bring-your-own kind, and we say which is which.)
If we shut down, are acquired and discontinued, or stop maintaining Neos Meet, its source code is released under an OSI-approved open source license — a binding commitment written into our terms and promised as §7 of the covenant. The software you build your work on can outlive us. You are never building on sand.
Who keeps the grounds
A steward that seeks fair pay for good keeping — not maximization — cannot hire an army; it stays a workshop, not a tower. So the honest thing is to tell you how small we are and where your money goes. We would rather say a rough true thing than a precise invented one.
Who builds it. Neos Meet is made by RSpond Inc. The whole team is one person, plus Claude Code — small enough that the person who answers your email is the person who can change the software.
Where your subscription goes. It pays for two things: the person who builds Neos Meet and answers your email, and the infrastructure that runs it — hosting and the database, transactional email, and error monitoring, the real cost centres named on our sub-processor list. No sales floor, no retention department, no lobby with a waterfall to fund — which is a large part of why the price can stay where it is.
The conversation
There is one door, and it is always open. Every message to support@neos.network is read by a person — there is no bot in front of us, and no ticket queue whose real job is to keep you from one. Replies to the emails we send you land in that same inbox. When you tell us what's missing or broken, it doesn't evaporate: bugs get fixed, and wishes climb the roadmap, with what we ship credited in the changelog. That loop — you talk, the software is allowed to change — is the whole idea.
Company details
The entity behind the terms and the privacy policy, and how to reach a person.
Want to know how your calendar data is handled?
The security page covers the scopes we request, where data lives, and the certifications we don't hold yet.
Read the security page