Ollasync

We’re building CampusTPO, a SaaS platform for simplifying training and placement management for educational institutions.

One decision we made early was to avoid overengineering the product.

It is tempting to start a new SaaS project with multiple services, complex infrastructure, and every modern technology available.

We decided to start differently.

## Start with the actual problem

Our first priority was getting the core product working reliably.

Instead of asking:

“What technologies should we use?”

we tried to ask:

“What does the product actually need?”

That changed how we approached the architecture.

We wanted the system to be:

- Easy to understand

- Easy to develop

- Easy to deploy

- Easy to maintain

- Flexible enough to grow

## Complexity has a cost

Every additional service or dependency creates another thing to understand, maintain, monitor, and troubleshoot.

That doesn't mean complex architectures are bad.

They are often necessary at scale.

But adding complexity before it is required can slow down a product that is still finding its direction.

For us, the principle became:

> Infrastructure should follow requirements, not trends.

## Security still matters

Keeping the architecture lightweight doesn't mean treating security lightly.

Authentication, access control, protection against common web vulnerabilities, rate limiting, password security, and audit-related functionality are considered part of the foundation.

We want the product to remain simple internally while still taking the important engineering requirements seriously.

## Building in public

CampusTPO is still evolving.

As the product grows, the architecture will also change when there is a genuine reason to change it.

That's one of the things I'm enjoying about building it: seeing which assumptions survive real development and which ones need to be reconsidered.

I'd be interested to hear from other founders and developers:

When building your SaaS, how do you decide when a simple architecture has reached the point where it needs to become more complex?

CampusTPO:

https://campustpo.com/

VPNs have become a basic part of staying safe online, but privacy is often hidden behind expensive subscriptions.

That’s why we’re building OllaVPN.

OllaVPN is a privacy-first VPN with a free plan that includes:

🔐 Post-quantum-ready security

🛡️ Kill switch protection

🌐 In-tunnel DNS

🔒 Peer isolation

🚫 No activity logs

🌎 Access to available countries

The goal is simple: make strong privacy protection accessible without forcing users into a premium plan.

The free plan is available now.

Try OllaVPN:

https://ollavpn.com/

Download:

https://ollavpn.com/dl/

We’d love to hear from other founders and builders:

What do you think a modern VPN should do differently?

Remote communication has become a normal part of how teams work, but the workflow around online meetings can still feel fragmented.

A meeting happens in one place, messages happen somewhere else, recordings may be stored separately, and follow-up conversations can become disconnected from the original discussion.

That was one of the problems behind Ollasync.

We wanted to explore a simpler approach to online communication where meetings, messaging, recordings, encrypted communication, and collaboration could work together as part of one workflow.

The idea is straightforward:

Meet → Communicate → Record → Follow Up → Collaborate

Ollasync is being built for people who work remotely and need a practical way to stay connected — from developers and startups to freelancers, students, and distributed teams.

We’re still building and improving the product, so the goal isn’t to claim that we’ve solved every problem with remote communication. Instead, we’re interested in learning what people actually need from their meeting and collaboration tools.

If you’re working remotely or building a distributed team, we’d love to hear what currently frustrates you about online meetings and collaboration.

You can learn more about Ollasync at https://www.ollasync.com/.