Tools for people who run their own servers.
Eleven products from one small studio: deploys, backups, cron, monitoring, error tracking, chat, mail and payments.
What we make
Each one started as something we needed for our own servers or our own shops. They share a stack, a voice and a Telegram bot.
dockxo
dockxo.comDeploy Docker apps to your own servers from one dashboard.
backupxo
backupxo.comBackups, restores and a data browser for MySQL and MariaDB.
cronxo
cronxo.comCron jobs for every server, in one place.
adminxo
adminxo.comMonitor, protect and manage Linux servers from one panel.
loggerxo
loggerxo.comError tracking for Laravel and the browser. Open source.
zingxo
zingxo.comChat with your visitors. Let an AI take the first reply.
urlxo
urlxo.linkShort links that show who clicked.
mailbuda
mailbuda.comOne calm place for the mail on every domain you own.
orcapayz
orcapayz.comRoute payments across all your Stripe accounts.
facetbrowser
facetbrowser.comEvery account gets its own browser.
clinicxo
clinicxo.comAppointments, prescriptions and patients for clinics with more than one branch.
How these get built
Your servers dial out
dockxo, cronxo and adminxo all run a small agent that connects outbound. No inbound port, no SSH key handed to a panel.
Your bucket, your keys
Backups go to storage you own. backupxo and dockxo write to your S3, R2, B2 or MinIO bucket; the dumps never touch ours.
Failures find you
Every product that can fail quietly has a Telegram alert. Successes stay quiet; a missed cron run or a rejected payment does not.
Free until it earns its keep
Most of the line-up is free with no seat limits. The ones that charge, charge once or only after they have made you money.
From the blog
All postsA short link's hot path: Redis, a 302, and a queue
How urlxo redirects without waiting for analytics, which characters it refuses to put in a code, and what it does not store about you.
ClickHouse for events, MariaDB for issues
loggerxo stores every event in ClickHouse and every issue in MariaDB. How the ingest path works and why one database was not enough.
Keeping a four-year-old CodeIgniter app healthy
clinicxo started in 2022 on CodeIgniter 3 and is still on it. What changed underneath it so that it could stay there.
Something broken, or something you wish one of these did?
One inbox for all eleven. We read everything; replies take a day or two.
Write to [email protected]