Why I Chose Go and SvelteKit

This is the first journal entry for my open source PaaS journey…

I chose Go because a lot of infrastructure and DevOps tools are built with it. Since I’m building a PaaS, I’ll be dealing with deployments, logs, networking, and long-running processes… so Go feels like a natural fit.

I also like the idea that Go can be lightweight and efficient, especially in the early stage of a product. Ariaseta Setia Alam mentioned this well in one of his LinkedIn posts:

“Ga perlu bayar server utk 100-1000 user pertama.”

Roughly translated: “You may not even need to pay for a server for your first 100–1000 users.”

That point stayed in my head… I want to build something simple, resource-friendly, and close to the infrastructure layer.

For the frontend, I chose SvelteKit because it feels simple. I come from a React background, but sometimes the React ecosystem feels too full of choices. SvelteKit feels calmer… it supports SSR, gives me what I need, and lets me focus more on building the actual product.

I also want to keep the project structure simple and readable… something closer to projects like Commento, where the folder structure already feels clear when you first open the repository.

And yes… I already started the journey with the first commit here: First commit of uploy

So for now, that’s the direction…

• Go for the backend and infrastructure side
• SvelteKit for the frontend
• simple structure
• less complexity
• more shipping

Let’s see where this journey goes…