Untitled

When building a SaaS application, it’s easy to think that more infrastructure automatically means a better product.

More databases. More services. More queues. More containers.

But sometimes, simplicity is the better engineering decision.

That’s one of the ideas behind CampusTPO.

We built the application around Bun and SQLite with WAL, keeping the core infrastructure lightweight while still providing a solid foundation for a modern SaaS application.

Instead of maintaining a separate database server, cache, or message queue from day one, the architecture focuses on keeping the application straightforward to develop, deploy, and maintain.

Authentication is also part of the foundation, including:

• Email/password authentication • Email verification • Google sign-in • Password recovery • Session management • Account management

Security wasn’t treated as something to add later either.

CampusTPO includes role-based access control, CSRF protection, Content Security Policy, rate limiting, password hashing, and audit trails.

The codebase is also separated into routes, services, repositories, and views, helping keep business logic and database operations independent from the user interface.

One of the biggest lessons from building CampusTPO has been this:

You don’t need complexity until your product actually needs it.

Redis, queues, microservices, multiple databases, and container orchestration can all be useful—but introducing them too early can create more things to maintain without solving an actual problem.

A simpler architecture can be easier to understand, debug, deploy, and evolve.

That’s the approach we’re taking with CampusTPO:

Start simple. Build securely. Add complexity when the requirements justify it.

If you’re interested in seeing what we’re building:

🔗 CampusTPO

Full link: https://campustpo.com/

I’ve been working on OllaVPN because I wanted to build a VPN that takes privacy seriously without making security complicated.

OllaVPN is designed around a simple idea: the important protections should be enabled by default.

It includes post-quantum-ready encryption, a modern WireGuard-based tunnel, in-tunnel DNS, peer isolation, continuous re-keying, and a kill switch designed to prevent traffic from leaking when the VPN connection drops.

I’m especially interested in the post-quantum side of things. Encrypted data captured today could potentially become vulnerable to future advances in computing, so I wanted OllaVPN to start preparing for that threat instead of waiting for it to become a problem.

The goal isn't to create another complicated VPN with dozens of settings.

It’s to make privacy something you can simply turn on and use.

OllaVPN is available here:

Download for Windows:

Technology and security details:

I used Zoom for almost 2 years.

It was my default whenever I needed to have a meeting, talk with someone, or discuss business.

But after a while, I started getting tired of meeting limits and restrictions.

So I decided to try something new: Ollasync.

And honestly, I really like how simple it is.

Create a meeting. Share the link. Join. Talk.

I’ve started using it for my personal calls and business meetings, and it has been a really good fit for me.

It also has features like video meetings, recordings, messaging, encrypted communication, and collaboration tools.

The funny thing is, I wasn’t actually looking for a “Zoom alternative.”

I just wanted something that made meetings easier.

Sometimes you don’t realize how much you’ve gotten used to a tool until you try something different.

For me, switching to Ollasync was one of those small changes that made my workflow a little easier.

👉 https://www.ollasync.com/