What is GitApp.si
It's a platform I built because I wanted it to exist. The idea: every developer should be able to spin up their own corner of the internet — a subdomain, a place to run tools, a place to share things — without dealing with servers, DNS, certificates, or any of that stuff.
So I made GitApp.si. You sign up, pick a name, and you get yourname.gitapp.si. Then you can use the tools I built, or write your own, or fork someone else's, or all three. Your subdomain, your stuff, your rules.
Why I built it
I kept running into the same problem. I'd find a useful online tool — JSON formatter, regex tester, whatever — and want to save my work, come back to it later, maybe share it with a coworker. But every tool wanted an account, or it didn't save state, or it disappeared after a week.
So I thought: what if I just owned the URL? What if alex.gitapp.si/json was mine, and I could bookmark it, and my recent JSON was always there when I came back? That's the entire pitch. It's selfish, basically. I built it for me.
The best dev tool is the one that lives at a URL you can actually remember.
How it works
Sign up, pick a subdomain name, and you're in. Your subdomain lives at yourname.gitapp.si. After that, you can use any of the pre-built tools (they're all on your subdomain too), or build your own using the CLI:
# install the CLI
$ npm install -g gitapp
# login and claim your subdomain
$ gitapp login
$ gitapp init --subdomain alex
# build a tool (any HTML/JS/Python file)
$ mkdir my-tool && cd my-tool
$ echo '<h1>hi</h1>' > index.html
$ gitapp deploy
→ live at alex.gitapp.si/my-tool
That's it. No Dockerfile. No nginx config. No "wait 24 hours for DNS to propagate". The CLI handles build, deploy, SSL, everything. You just write code.
The stack
Frontend is plain HTML/CSS/JS — no framework needed for a static site, and the load time stays under 200ms. Backend runs on a small fleet of VPS instances with a simple Go API in front. Tools you build run in isolated containers with CPU and memory limits so one heavy tool doesn't take down everyone else.
For storage I use Postgres for user data and S3-compatible object storage for any files you upload. CDN in front of the static stuff for speed. The whole thing is open source — the platform, the CLI, the pre-built tools. MIT licensed, so fork away.
What's next
Right now I'm working on: real-time collaboration on tools (so you and a friend can edit the same regex pattern at the same time), a marketplace where you can publish tools for others to use, and team subdomains (so myteam.gitapp.si has shared tools for the whole crew).
I also want to add support for scheduled tasks. So you could write a tool that runs every hour, hits some API, and saves the result to your subdomain. Cron-as-a-service basically, but tied to your tools.
Found a bug? Open an issue on GitHub. Have an idea? Same place, or hit me up on Discord. I read everything and respond to most things — usually within a day, sometimes within an hour if I'm awake.
If you want to follow along with what I'm building, I post updates on Twitter and write a devlog on the blog. No email list though — I know those are annoying.