Oleksandr

ServersCamp v2.0.0 • Warden: security on the wire, both directions serverscamp.com/changelog/v2.0…

I knew my SSH was being brute-forced. Everyone knows that, in theory. Then I built a dashboard that shows it live - IPs, countries, ports, attempt counts, reputation flags. Watching it happen to my own box felt different. And once you see it, you kind of want it gone.

L4 load balancer that sees everything and blocks attacks? Yeah

Today’s “I knew this, but still” moment: I pointed a test load balancer at an empty server. No website, no domain, no shared IP. In 24h, 113 sources from 20 countries found it and started probing. Public IPs are never really idle. serverscamp.com/blog/the-backg…

Let's reinvent load balancers👀

ServersCamp v1.3.0 • Port forwarding from default router • New VMs back up off-site by default • Bugfixes serverscamp.com/changelog/v1.3…

ServersCamp v1.2.0 • Public domain names and reverse DNS for your servers • Internal DNS for your private networks serverscamp.com/changelog/v1.2…

ServersCamp v1.1.0 • Changelog: versioned releases • SSH keys: safer management • Cloud Panel: What's new in your sidebar • Cloud Panel: faster resource lists with quick actions • Virtual Machines: install from a custom ISO serverscamp.com/changelog/v1.1…

On January 1st my cloud got its first public tester. Since then, most of my attention has gone into stability and new features. Recently I turned on test billing to debug how the platform meters resources, and built this dashboard to make the numbers easier to inspect. It is not confirmed MRR yet, but seeing the meter move makes me happy.

Alright. Backups and snapshots are done. Probably the most brain-melting thing I've built. I didn't want to clone anyone, so from the start I did it the way I see it: 1. Snapshots are separate disk copies, in the same SDS as the original disk. Fast, hot, recovery level is operational, saves you from your own mistakes. 2. Backups. This is where I dragged in enterprise and their compliance stuff. Backups are encrypted, backups are compressed, by default they go to another country, another storage, another organization. Their failure domain is all of ServersCamp, or a whole country. They get regularly tested for restore: checksum verification, plus a check that boot actually works. Also separate GFS presets. What I like most is how easy it turned out for the user. No settings needed, just one checkbox and you get an enterprise DR backup.

One small tag for LET, one giant leap for ServersCamp 🚀

Think the VM create wizard looks better now

Implementing one of the missing low-level bricks: snapshots. Per-node agent, listening to the bus.

@Shpigford Working on exactly this stack. Postgres + agent-native MCP provisioning shipped, Redis coming. Not ready to recommend yet, happy to ping you when it’s there.

Agent-friendly hosting providers? Specifically for Rails + Postgres + Redis. Ideally with a history of stability, especially over the past 6-12 months.

@_swanand Don't blame Google too fast, they most likely did what they were supposed to. Policy violation, unpaid invoice, abuse report... accounts don't just get blocked for fun.

Never build your business on GCP. This is an incredible risk surface area.

@sandislonjsak The real issue isn't GitHub specifically, it's the blast radius of shared multi-tenant architectures. GitLab or Bitbucket have the exact same failure mode. If you want real isolation, self-host (GitLab CE works great).

I think it’s time to migrate from GitHub to something else. Any recommendations? GitLab? BitBucket?

@zo0r @benjamin_ACD @AvgDatabaseCEO @Railway @neondatabase I would say even 10 minutes is a disaster, not hours. Anything beyond that means your HA story is broken.

@benjamin_ACD @AvgDatabaseCEO @Railway @neondatabase for my standards +4 hours outage is very bad

we migrated our production apis 1 hour ago after a 40-minute outage. more than 2 hours later, @railway is still down. @railway is for cloud what @neondatabase is for databases. since our platform launch, we've had three outages. guess who was behind every one? yes, @railway. big mistake trusting you.

@Shpigford @Railway @Hetzner_Online @digitalocean Splitting apps and DB across two providers is rough -cross-provider latency on every query, and Hetzner doesn't have real HA for VMs (a host dies, your VM dies with it). That's exactly why I'm building my own cloud: proper HA, apps and DB in the same fabric, no cross-cloud hops.

nothing i can do about 6 apps/services being down right now (see: @railway outage), but here's my plan for in the morning after i've had a fresh night of sleep... 1. move all web services to @Hetzner_Online 2. move all postgres databases to @digitalocean 3. manage it all with @hatchboxio i've got this exact stack for other things, so i'm exceedingly comfortable with it. will just be scaling it all up to handle more apps. all of the affected apps are rails + postgres.

@rfgarcia Weird that they depend on Google, I thought Railway ran their own infra?

“Migrate off Railway, make no mistakes”

@JustJake Hang in there, shit happens. This is exactly why I run my own cloud on bare metal, no third-party dependencies, no upstream to wait on. Hope GCP unblocks you fast.

It appears Google Cloud has blocked our account, and so some services are unavailable We’ve escalated this to Google and will keep people posted. Deepest apologies.