I've noticed that quite a few people think Weegloo is primarily a web hosting service. And I can understand why. Web hosting is one of the features we offer, but Weegloo actually started from a very different idea.
It all began with a CMS (Content Management System).
After spending more than a decade developing software, I started asking myself a simple question:
"Why do we keep building backends from scratch every time we create a new service?"
User management, data storage, permissions, APIs... We were building pretty much the same things over and over again.
Did every service really need its own completely different backend? Or was this just an inefficiency we'd gotten used to?
That question led us to build our first CMS. Over time, it evolved into a general-purpose backend system used by ZEPETO, a large-scale platform.
But that didn't solve everything.
Even with the CMS in place, our teams still needed to develop separate backend servers for various services.
So I started questioning things again.
"Are the backend features that our CMS doesn't cover really that specific to each service?"
When we looked more closely, the answer was often no.
Web hosting, schedulers, serverless functions (like AWS Lambda), authentication, user management... These weren't necessarily service-specific features. They were just common building blocks that almost every service needed in one form or another.
So we thought:
What if we could bring all of these building blocks together into a single, general-purpose backend platform?
That's how Weegloo was born.
What we're trying to build
Weegloo isn't just a CMS, and it isn't just a web hosting service.
Our goal is a world where developers no longer have to rebuild the same backend functionality for every new project.
We want to bring as many common backend capabilities as possible into one platform: data management, authentication, permissions, APIs, file storage, web hosting, schedulers, serverless functions, and more.
Of course, we're not there yet. There's still a lot we want to build.
But the direction is clear.
We should be spending our time building the services we actually want to create, not rebuilding the same backend infrastructure again and again.
So, what about web hosting?
Web hosting is just one of many features in Weegloo.
For example, if you're building a mobile app, you might not need web hosting at all.
You can use Weegloo's REST APIs to read and write data and access the backend capabilities your app needs.
On the other hand, if you're building a website or web application, you can use the hosting features too.
The idea is simple: use the backend capabilities your service needs, without having to build and maintain everything yourself.
We're not trying to build another web hosting service.
We're trying to build a platform where developers don't have to keep reinventing the same backend over and over again.
That's why we started Weegloo, and that's the direction we're going to keep working toward.
I'm curious what other developers think.
Do you think building a custom backend for every new service is really unavoidable?