Today we're launching Meeto, our fifth product. It's a video meeting tool, which means we owe you an explanation. The video call market is not exactly empty. Zoom, Google Meet, Teams, and a dozen smaller players already fight over it. So why build a fifth product, and why this one?

The honest answer is that we kept hitting the same wall in our own work. Every product team at KeepFlow talks to customers, contractors, and each other all day. And every day, someone lost two or three minutes to the same ritual: send a link, wait for the other person to install an app, watch them create an account, approve them out of a waiting room, then finally say hello. Multiply that by every call, every person, every week, and it becomes a tax on getting anything done.

Meeto is our attempt to delete that tax. The entire product is built around one sentence we wrote on a whiteboard and never edited: joining should take seconds.

Why a fifth product

We have a rule at KeepFlow: we don't build a product unless we'd use it ourselves every day and can't find something that already does the job well. Meeto cleared both bars.

The "already does the job" part is where the incumbents fall short in a specific way. They optimize for the scheduled, calendar-invited, corporate meeting — the recurring standup with fifteen people. That's a real use case, and it's well served. But a huge share of actual conversations are spontaneous: a quick "can you hop on for five minutes," a customer call from a support thread, a contractor walking you through a design. For those, the setup overhead is a bigger fraction of the total time than the conversation itself.

Nobody was treating the spontaneous call as the primary case and designing everything else around it. That was the gap.

Joining should take seconds

Here's what that principle forced us to build, and what it forced us to throw away.

  • No account for guests. You click a link, your browser asks for camera and mic, and you're in. There's no sign-up wall between a person and the room. Accounts exist for hosts who want a booking page and history, but they're never required to talk.
  • No install, ever. Meeto runs entirely in the browser on WebRTC. Desktop, phone, tablet — if it has a modern browser, it works. We spent a lot of engineering effort making the browser experience good enough that a native app would add nothing, because a native app is a download, and a download is not seconds.
  • No lobby by default. Waiting rooms are a security feature that most calls don't need. So we made the door configurable instead of mandatory, and defaulted it to open.

Throwing away the install and the guest account sounds simple. It isn't. It means the browser path has to be flawless — permissions, echo cancellation, reconnection when someone's WiFi drops, mobile Safari's quirks. That's where most of the work went.

Door modes: open, knock, or password

Removing the lobby doesn't mean removing control. It means putting the host in charge of how much friction the room has, instead of forcing the same friction on everyone.

Every Meeto room has one of three door modes:

  • Open — anyone with the link walks straight in. This is the default, and it's right for the majority of calls: internal chats, customer calls where you sent the link yourself, quick syncs.
  • Knock — guests land in a holding state and the host admits them one by one. This is the classic waiting room, available when you actually want it: interviews, sensitive conversations, public links you're not sure about.
  • Password — the room requires a code you share out of band. Good for links that might get forwarded, or recurring rooms you don't want strangers wandering into.

The point is that the safe-but-slow option is one click away, not the starting position. Most people never leave Open, and that's fine, because the link itself is the credential.

Beyond the door, hosts get the controls you'd expect: lock the room once everyone's in, mute or remove a participant, promote a co-host, and end the meeting for everyone at once.

Drawing on the screen and AI recaps

Two features earned their place because they came up over and over in how we actually use calls.

The first is annotation over screen share. When someone shares their screen, anyone can draw on it — pen, shapes, arrows, text — and everyone sees it live. It sounds small until you're reviewing a design or debugging a layout and you can just circle the thing instead of describing where it is. It works from mobile too, so the person on their phone isn't a second-class participant.

The second is AI recaps. When a call ends, Meeto produces a searchable transcript with speaker labels, a short summary, and a list of action items, and drops it in your inbox. Nobody has to volunteer to take notes, and nobody has to rewatch a recording to find the one decision that mattered. On the free plan you get two hours of recaps a month; Pro raises that to ten, alongside cloud recording.

Booking, built in

The last piece closes the loop from "let's find a time" to "we're talking." Every Meeto account comes with a personal page at meeto.me — your own booking link. You define meeting types, set your working hours and buffers, connect your calendar so you're never double-booked, and share the link. Someone picks a slot, and a Meeto room is waiting for both of you when the time comes.

This matters because the scheduled call and the instant call are the same product now. You're not bouncing between a scheduling tool and a video tool that don't know about each other. The time you book is the room you join.

Pricing

Meeto is free to start, and the free tier is meant to be genuinely useful, not a trap: 60-minute group calls, up to 10 participants, screen sharing with drawing, chat and reactions, a basic booking link, and two hours of AI recaps a month.

Pro is $7 a month. It lifts calls to unlimited length and up to 25 participants, adds ten hours each of cloud recording and AI recaps, gives you the full meeto.me booking page with up to five connected calendars, and adds reminders and time-zone-aware slots. For teams that need to run it themselves, there's a self-hosted enterprise option with your own domain and infrastructure.

We built Meeto because we were tired of the thirty seconds before every conversation. If that resonates, the fastest way to understand it is to open meeto.me, create a room, and send the link to someone. That's the whole pitch — it should just work, in seconds.