The story behind the project
About TikaCam
TikaCam is an independent video chat project. It's built and maintained by one person — me, Aitor — from Switzerland. This page is the honest version of what TikaCam is, why it exists, and where it's going.
Who's behind TikaCam
I'm Aitor. I've been writing code since CPUs had a single core and modems were slower than 56k. I've watched the web grow up: dial-up, broadband, IRC, MSN, Skype, the cloud, WebRTC. Every step made it easier to connect people in real time — and every step made me want to build something with all that new power.
By day, I'm a systems engineer in Switzerland. I run production clusters in industries where downtime isn't a small inconvenience — banks, hospitals, places where the systems matter. That work taught me to take reliability seriously. You can't ship something flaky to a hospital.
By night, I work on TikaCam. It's the project I always wanted to build: something useful, scalable, and genuinely fun. A way to connect people across the world in real time, without an account, without a feed, without an algorithm deciding for them.
Why I built it
The idea is older than the site. Back in the IRC and Skype days, I'd think: how do you take this — strangers talking in real time — and open it to the whole world, no signup, with video? Browsers couldn't do it then. Bandwidth couldn't do it. The cloud couldn't do it.
By the early 2020s, all three could. WebRTC made peer-to-peer video work natively in the browser. Cloud infrastructure made it cheap to run. And then Omegle shut down in November 2023, leaving millions of people with nowhere to go that felt right. The remaining alternatives kept the same model: random matching, hit "next", hope. That's never been my favorite design.
I bought tikacam.com a while before launching anything. I didn't want to rush. The idea I kept coming back to was simple: what if you could see who's online before you connect to them? That's it. That's the whole concept. The picture wall.
The picture wall idea
Random matching wastes everyone's time. You skip, they skip, nobody gets to choose. The picture wall flips that: real-time snapshots of who's online, you pick someone whose vibe seems right, you call. They accept or they don't. That's a normal human dynamic, the same way you'd approach someone at a real event.
Building it scalable was the hard part. Continuous low-latency snapshots from every connected user, AI moderation on the public wall (private calls stay peer-to-peer and untouched), TURN/STUN servers for NAT traversal, the orchestration to keep it responsive when the room is full. None of it is rocket science individually — but stitching it all together, on a side-project budget, took time.
The moment it became real
A few weeks after the first version went live, I was testing TikaCam with a friend over Discord, just to see if the wall felt right. While we were poking around, a stranger from another country showed up on the wall. My friend called him. They started talking. Just like that.
That's the moment I knew the site actually worked. Not because the code ran without errors — but because two strangers from two corners of the world had a real conversation, on something I'd built. That memory still makes me smile.
Words from a user
A year ago, after I posted TikaCam on Product Hunt, a user named Star Boat — a co-founder with a long, active history on the platform — left a comment that stuck with me. He said the picture wall was a unique twist on video chat, and that he wanted to try it. Spontaneous feedback like that is rare for a small project, and it kept me building.
What I've learned along the way
TikaCam taught me more than I expected. On the technical side: Linux at scale, Docker and containerization, WebSocket plumbing, the Node.js ecosystem and its packages, Cloudflare for the edge, WebRTC and PeerJS, TURN and STUN servers, and a long tail of smaller things you only learn by hitting them in production. If you're curious about how the call flow actually works end-to-end, I wrote it up on the how it works page.
On the human side: that most progress comes from failure. Most of what I tried first didn't work. Performance was bad. UX was confusing. Servers fell over. Each time I learned something I couldn't have learned by reading. That's how you build anything real.
A timeline
I bought the tikacam.com domain. The idea was older — I just needed time to design something I'd actually want to use myself.
First version goes live. The picture wall works. It's slow, ugly, and incredible to me.
Testing with a friend, a stranger joins the wall and they start talking. The site actually works.
Iteration. WebRTC tuning, TURN/STUN servers, AI moderation on the picture wall, Cloudflare layer. Lots of failures. Each one taught me something.
Full redesign. Cleaner, faster, more honest about what TikaCam is and what it isn't.
A small, independent project. Some people meet here every day. That was always the goal.
What TikaCam is — and what it isn't
What it is: a free, browser-based video chat with a real-time picture wall. You see who's online, you choose who to call, the call runs peer-to-peer with WebRTC encryption. No signup. No email. No algorithm steering you anywhere. If you want to chat online with someone you actually picked, instead of being randomly paired, that's the whole product.
What it isn't: a giant social platform. A startup chasing growth at all costs. A site funded by ads or selling your data. There's no premium tier, no upsell, no metrics dashboard pretending to be more than it is.
My honest goal is simple: have a few people meeting on the wall at any given moment, somewhere in the world, having a real conversation. That's it. If TikaCam grows beyond that, great. But I'm not optimizing the project against a growth chart — I'm optimizing it against whether the experience is good for the person on the other side of the call.
Privacy and how the site is built
Calls are peer-to-peer. Your video and audio go directly between you and the person you're talking to — they don't pass through TikaCam servers. I genuinely cannot see, record, or store call content, even if I wanted to. WebRTC encryption is on by default; that's not a feature I added, it's how the protocol works.
The only thing that touches a server is the small, public picture wall snapshot, which is reviewed by AI moderation before anyone else sees it. That's there to keep the wall from turning into something it shouldn't be. Once you start a call, you're off the wall and into a private peer-to-peer connection.
And if something goes wrong on the other side of the call — or if you spot inappropriate content on the picture wall before connecting — there's a Report button available both on the wall and during the call itself. Reports are reviewed and acted on; they're how we catch what AI moderation can't.
For the legal version, see the Privacy Policy. For more on safety and the report system, see the Safety page.
Get in touch
If something's broken, if you have an idea, or if you just want to say hi — Discord is the best place. I read everything, even when I take a while to reply. There's no support team. It's just me.
You can also find TikaCam on Telegram and Product Hunt.
TikaCam is built and maintained by Aitor, an indie developer based in Switzerland. The project is independent and self-funded.