Docs
Ethos
Why Sidekick

Why Sidekick

Let’s face it. Marketing money has ruined developer tools market. It’s true whether you accept it or not. The result however, is crippling methods to do simple things. Complexity solved by certain key players for massive margins. Complexity that doesn’t need to be there. I am sick of it and it’s time for a change.

Your side project doesn’t need hyperscaling, kubernetes or even regions - most of the time. Your side project need to be production ready safely and quickly; in mins not hours. That’s what Sidekick is meant to do. Simplify hosting and take your app from your machine to the whole world in mins. I built Sidekick because deploying things now sucks, except for fly.io. It’s either too expensive, too complex or too much features.

I built Sidekick to bridge that gap in the market and honestly just for myself. To make deploying whatever I dream easier. I don’t want to spend hours scrolling docs of whatever PAAS I use; I already know docker. This is also why I insist on wizard vs config - Sidekick will ask you the right questions to get you started. You can dig deeper if you need to.

That being said, Sidekick didn’t come out of thin air. I’m heavily inspired by the following:

Vision