Coolify vs Railway and Render: what self-hosting really costs
> TL;DR
>
> - What you get: a side-by-side monthly bill for one small web app plus Postgres on Coolify (self-hosted and Cloud), Railway, Render and Hubfly space, plus a worksheet for the hours self-hosting takes.
> - Who it's for: developers and small teams deciding between "my own server with Coolify" and "a platform that runs it for me".
> - Time to read: 10 minutes. Prices checked on 4 November 2026.
> - Short answer: for one or two small apps, a managed platform is usually cheaper _and_ less work. Coolify starts to win at roughly 5 to 12 small apps on one server, depending on whether they share a database and how much memory they need, if you're happy owning backups and updates.
Your Railway or Render bill keeps creeping up, and Coolify looks like a free way out. You rent a server, run one install command, and get Git deploys, databases and HTTPS in a nice dashboard. No platform bill.
But the server isn't free, the backups aren't automatic until you set them up, and nobody patches it for you. This guide puts real numbers on both sides, so you can pick the option that costs you less in money _and_ in evenings.
Try it on Hubfly space: the free tier gives you 360 hours a month, no card needed.
What Coolify is (and why people love it)
Coolify is an open-source, self-hostable platform. You connect your own servers and it handles Git deploys, Docker images, Compose stacks, one-click services and databases.
It's a good piece of software, and it wins on several things:
- No platform fee if you self-host. The self-hosted edition is "Free forever" with every feature, per Coolify's pricing page.
- Many apps on one bill. You pay for the server, not per app. Ten tiny apps can share one box.
- Real database backups. Coolify can schedule backups for PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse and SQLite, and upload a copy to any S3-compatible storage (backups docs).
- Portability. It runs on almost any Linux box: a VPS, a dedicated server, even a Raspberry Pi.
- No lock-in. Your apps are plain Docker containers on a machine you control.
If you already run Linux servers for a living, Coolify is a great tool. The question is what it costs everyone else.
The two ways to run Coolify
Self-hosted. You install Coolify on your own server. The install guide asks for at least 2 CPU cores, 2 GB RAM and 10 GB of disk, on a supported Linux distribution, with SSH access and the right firewall ports open. Then you run one script.
Coolify Cloud. The Coolify team runs the dashboard for you. It costs $5 a month for up to 2 connected servers, plus $3 a month for each extra server, and you still bring and pay for your own servers (pricing). The upside: the control plane's updates and backups are managed, and your server only needs room for your apps.
Either way, the server running your apps is still yours to look after.
The reference app
Whether you're weighing Coolify vs Railway or Render, every option below runs the same small setup:
- One web app, always on, about 512 MB of memory.
- One small Postgres database.
- Low traffic: a side project, an internal tool or an early-stage SaaS.
Bandwidth is left out because the plans bundle it very differently. Check it separately if you serve a lot of files or video.
The monthly bill, side by side
Prices from each vendor's official page on 4 November 2026, in US dollars, before tax.
| Option | What you pay for | Monthly cost | Backups included in that price? |
| --- | --- | --- | --- |
| Coolify self-hosted on a DigitalOcean Droplet (2 vCPU, 2 GiB, $18) | Server + weekly server backups (20% of Droplet price) | $21.60 | Weekly server image. Database dumps to S3 are free to set up in Coolify, plus storage cost |
| Coolify Cloud + a 1 vCPU / 2 GiB Droplet ($12) | $5 Coolify Cloud + server + weekly backups | $19.40 | Same as above; Coolify itself is backed up for you |
| Railway Hobby | $5 plan that includes $5 of usage, then usage | about $10.81 (see math below) | Built-in database and volume backups are listed on the pricing page; check which plans include them |
| Render | $7 web service (512 MB) + $6 Postgres (256 MB) | $13.00 | Yes: logical backups on paid Postgres instances, plus point-in-time recovery (window depends on your workspace plan) |
| Hubfly space | Dedicated container (0.5 vCPU, 512 MB, always on) + Managed Postgres Nano | $4.26 | No automatic database backups yet. Use manual exports |
A few honest notes on that table:
- Railway bills measured usage, so a busier app costs more. Hubfly space bills the CPU and memory you allocate per hour, so its bill changes only when you resize or add containers. Render, Droplets and Coolify Cloud are fixed monthly plans.
- Render also offers up to $10K in migration credits for teams moving production workloads (pricing page). That can matter more than a few dollars a month.
- Hubfly space's database has no automatic backups or point-in-time recovery today. Its pricing docs say automatic backups are "coming soon" and point you to manual exports. On that one point, Coolify's scheduled S3 backups are ahead.
!The cost panel for a 1 vCPU, 1 GB always-on container: $4.42 a month
_The Create Container cost panel shows the monthly price before you deploy. Here: 1 vCPU and 1 GB, always on._
How the numbers are calculated
You can redo every line yourself. Months are 730 hours.
Hubfly space (rates from the pricing page: CPU $0.004 per vCPU-hour, RAM $0.002 per GB-hour, storage $0.00001536 per GB-hour):
- Web container, 0.5 vCPU / 512 MB / 4 GB disk, always on:
0.5 × 0.004 × 730 = $1.46, plus 0.5 × 0.002 × 730 = $0.73, plus 4 × 0.00001536 × 730 = $0.04. Total $2.23.
- Managed Postgres Nano (0.25 vCPU, 512 MiB, 10 GiB), from the database pricing docs: compute $0.002 per hour + system disk $0.00001536 + 30% management fee $0.0006 + storage $0.0001536 = $0.00276896 per hour. About $2.02 a month.
- Together: $4.26. Want a full vCPU and 1 GB for the web app instead? That container is $4.42 (screenshot above), so the total is $6.44.
Railway (rates from the pricing page): $0.00000772 per vCPU-second ($20.29 per vCPU-month), $0.00000386 per GB-second ($10.14 per GB-month), volumes $0.00000006 per GB-second ($0.16 per GB-month). Railway bills what your app actually uses, so the bill depends on load. Assume:
- Web app averages 0.1 vCPU and 512 MB: 0.1 × 20.29 + 0.5 × 10.14 = $7.10.
- Postgres averages 0.05 vCPU, 256 MB and a 1 GB volume: 0.05 × 20.29 + 0.25 × 10.14 + 0.16 = $3.71.
- Usage $10.81. The $5 Hobby plan includes $5 of usage, so the bill is about $10.81.
Render: $7 (web service, 512 MB) + $6 (smallest paid Postgres, 256 MB) = $13, on the free Hobby workspace.
Coolify self-hosted: the smallest Droplet that meets Coolify's 2-core, 2 GB minimum is 2 vCPU / 2 GiB at $18. Weekly Droplet backups cost 20% of the Droplet price ($3.60). Total $21.60. Daily backups are 30% ($5.40), for $23.40.
Coolify Cloud: $5 + a 1 vCPU / 2 GiB Droplet at $12 + 20% weekly backups ($2.40) = $19.40.
Coolify's own docs often suggest Hetzner, which is usually cheaper than DigitalOcean. On 4 November 2026, though, Hetzner's Regular Performance page listed its plans as "currently unavailable", so it isn't in the table. If you can get a Hetzner server, redo the Coolify rows with its price.
The cost nobody puts in the table: your hours
A platform bill is only half the price. With self-hosted Coolify you also own:
1. The server. OS updates, SSH keys, firewall rules, disk space. Docker images and old builds fill disks quietly.
2. Coolify itself. You can turn on automatic updates, which install new releases on a schedule (daily at midnight by default, per the update docs). The dashboard restarts briefly during an update, and the docs advise taking an instance backup and reading the release notes first.
3. Security. Coolify's automated install needs root access to your server, so its bugs matter. Its GitHub repository lists 70 published security advisories as of 4 November 2026. Publishing them openly is a good sign, but someone on your team needs to read them and update promptly.
4. The first-login race. The install guide warns that whoever reaches the registration page first becomes the admin, with root access to your server. Create your admin account right away, or pre-create it with the install variables.
5. Backups and restores. Coolify's own docs say it plainly: "A backup is not a restore test." You need an S3 bucket, a schedule, a retention rule and an occasional practice restore.
6. Outages. One server means one point of failure. When it goes down at 2 a.m., you're the on-call team.
A worksheet for your own time
Use these as starting estimates and adjust them to your experience.
| Task | First month | Each month after |
| --- | --- | --- |
| Create server, SSH, firewall, DNS, install Coolify | 2–4 h | – |
| Set up S3 backups and do one practice restore | 1–2 h | 0.5 h (restore test) |
| OS and Coolify updates, advisories, disk cleanup | – | 0.5–1 h |
| Something breaks | – | 0–2 h |
| Total | 3–6 h | 1–3.5 h |
Multiply the monthly hours by what an hour of your time is worth. At $30 an hour, even 1 hour a month adds $30, more than the whole self-hosted server bill. That's the real comparison.
If you enjoy running servers, or you're learning, those hours aren't a cost. They're the point. That's a perfectly good reason to choose Coolify.
When Coolify wins on money: many small apps on one server
The managed rows grow with every app. The self-hosted row is flat until the server is full.
Using the numbers above (a $21.60 Droplet with backups vs $2.23 per always-on Hubfly space container):
| Small apps | Hubfly space, all sharing one Nano Postgres | Hubfly space, each with its own Nano Postgres | Coolify, 2 GiB Droplet + backups | Coolify, 4 GiB Droplet + backups |
| --- | --- | --- | --- | --- |
| 1 | $4.26 | $4.26 | $21.60 | $28.80 |
| 3 | $8.73 | $12.77 | $21.60 | $28.80 |
| 5 | $13.20 | $21.28 | $21.60 | $28.80 |
| 7 | $17.67 | $29.79 | $21.60 | $28.80 |
| 9 | $22.14 | $38.31 | $21.60 | $28.80 |
| 12 | $28.84 | $51.07 | $21.60 | $28.80 |
On the smallest server Coolify supports, it breaks even at about 5 apps that each need their own database, or about 9 apps sharing one. Size the server for that many apps (4 GiB) and the break-even moves to about 7 and 12. Two caveats keep this fair:
- The apps share 2 vCPUs and 2 GB on the Droplet, and Coolify uses some of that itself. Nine always-on 512 MB containers on Hubfly space get 4.5 vCPUs and 4.5 GB between them; nine 512 MB apps won't fit in 2 GB next to Coolify. In practice, budget a 4 GiB Droplet ($24, or $28.80 with weekly backups) for that many apps, which moves the break-even point further out.
- Staging and hobby apps don't need to run all night. With Auto Sleep on, a 0.5 vCPU / 512 MB Hubfly space container shows $1.14 a month in the cost panel, which pushes the break-even point further out.
Which should you pick?
Pick Coolify self-hosted if:
- You run several small apps (about 5–7 if each needs its own database, about 9–12 if they share one, depending on server size) and want one flat bill.
- You already maintain Linux servers, or you want to learn.
- You need full control over where data lives, or to run on hardware you own.
- You'll actually set up S3 backups and test a restore.
Pick Coolify Cloud if: you like Coolify's workflow and own servers, but don't want to babysit the dashboard itself.
Pick Railway or Render if: you want an established managed platform, you rely on one of its specific features, and the bill fits. Render's migration credits can make a move nearly free for a larger team.
Pick Hubfly space if: you want managed containers with the lowest bill in this comparison for one or two small apps, a price you can see before you deploy, and a monthly budget cap per project. Just plan your own database exports until automatic backups ship.
!Project budget cap set to $10, with the projected monthly cost shown
_A project budget cap sets a hard monthly limit for the project, with emails at 80% and 90%, so a mistake can't run up a surprise bill._
What can go wrong
1. "My Coolify server ran out of disk." Old images, build caches and local backups pile up under /data/coolify and Docker's own folders. Set backup retention in Coolify, upload backups to S3 with "Delete after S3 upload", and prune unused images on a schedule.
2. "My backup job says Success but I can't restore." A file existing isn't proof it restores. Restore into a throwaway database once a month and point a copy of your app at it.
3. "My managed bill is higher than the table." Usage-billed platforms charge for what you actually run. A bigger instance, a second replica or a chatty worker changes the math. Check each platform's cost estimate before deploying, and set a spending cap where the platform offers one.
Try the managed side in a few minutes
Deploying a container image on Hubfly space is short:
1. Create a project and pick a region. Set a monthly budget cap under Advanced Options if you want a hard limit.
2. Click Create → Create Container, choose Docker image, and enter your image, like your-org/your-app:1.0.
3. On Resources, choose Dedicated Tier, set CPU and memory, and turn Auto Sleep off for an always-on app. The cost panel updates as you move the sliders.
4. Click Deploy Container. A small image is running in well under a minute.
5. Open Network → Add Domain → Auto Endpoint and pick your port. You get an HTTPS address like your-app.eu1.hubfly.app, about a minute after clicking Deploy for a small image.
!A dedicated container running, with 1 vCPU and 1 GB
_The container page after deploy: status, tier and resources at a glance._
!The Network tab with an HTTPS subdomain routed to port 80
_Network → Add Domain creates an HTTPS subdomain with TLS on by default._
For the database, create a Managed service project, choose PostgreSQL and the Nano size, and copy the connection string into your app's environment variables. See how to get a managed PostgreSQL database for about $2 a month.
Takeaway
Coolify is free software, not free hosting. For one or two small apps, a managed platform is often cheaper than the server Coolify needs, before you count a single hour of your time. Once you run roughly 5–7 small apps that each need their own database (or 9–12 that share one), and you're comfortable owning backups and updates, Coolify on one server becomes the cheaper, flexible choice.
Read next:
- Fixed vs pay-as-you-go hosting: find your break-even point
- Best Heroku alternatives in 2026: 7 options and what they cost
- Deploy a docker-compose.yml as-is: 8 platforms compared
Go further on Hubfly space
- Moving from Railway? Follow how to move your app from Railway to Hubfly space, step by step.
- Store backups and files in Hubfly space Storage, S3-compatible buckets at about $0.011 per GB-month. A Coolify backup bucket works too.
- Deploy on every push with GitHub Actions and a deploy webhook.
Run the numbers for your own app with the Hubfly space pricing calculator, or start free on Hubfly space: 360 hours a month, no card needed.
1 reaction
I open-sourced Coolify.
coollabsio/coolify
Now @heyandras fears me.
24 likes · 4,692 views
Shoutrrr: alternative to Buffer Essentials ($60/yr) #Shorts
A self-hosted social media scheduler: write a post once, send it to several networks at the same time, or queue it on a schedule.
The pairing is the project's own: the README calls it an open-source alternative to Buffer, Typefully and Hootsuite. It publishes to X, Bluesky, LinkedIn, Facebook Pages, Instagram, Threads and Discord, splits long posts into threads where a network allows it, and tracks followers and engagement. Buffer charges per channel, so sixty dollars is the saving for one, every extra channel adds to it, and this is another item that is not an AI tool.
Replaces Buffer Essentials at $60 a year (one channel, billed yearly; $5/mo monthly).
The catch: You run it on your own server and register your own developer apps with X, LinkedIn and Meta. LinkedIn analytics do not work for personal accounts, and Buffer's free plan already covers three channels.
Apache-2.0 licence, 471 GitHub stars (checked 2026-10-28). coollabsio/shoutrrr
Full episode: youtu.be
#FUBARAI
2 views
yesss @coolify.io v4.5.0 introduced passkeys github.com/coollabsio/coolify/releases/tag/v4.5.0
3 likes
Coolify : un PaaS auto-hébergeable, alternative Open Source à Vercel, Heroku et Netlify. Il permet de déployer des sites statiques, des bases de données, des applications et plus de 360 services en un clic, sur vos propres serveurs
👉 coollabsio/coolify t.co
46 likes · 4 reposts · 2,341 views
Coolify : un PaaS auto-hébergeable, alternative Open Source à Vercel, Heroku et Netlify. Il permet de déployer des sites statiques, des bases de données, des applications et plus de 360 services en un clic, sur vos propres serveurs
👉 coollabsio/coolify
10 likes · 2 reposts
不用雲端也能克隆聲音， VoiceStudio 支援 646 語言做影片配音
今天 GitHub 熱榜，VoiceStudio 一天狂噴 1,592 顆星。TradingAgents、claude-seo、coolify、thinkrail 也上榜。VoiceStudio 是免本地 ElevenLabs 替代，646 語言。TradingAgents 多 agent 交易框架。claude-seo 審網站。coolify 自架 PaaS。thinkrail Vibe IDE。
1｜VoiceStudio：免本地語音
debpalash/VoiceStudio
2｜TradingAgents：AI 交易
TauricResearch/TradingAgents
3｜claude-seo：SEO 神技
AgriciDaniel/claude-seo
4｜coolify：自架 PaaS
coollabsio/coolify
5｜thinkrail：Vibe IDE
JetBrains/thinkrail
資料來源：GitHub Trending（今日新增 star）
每天幫你篩一遍 GitHub 開源熱榜。
排名依 GitHub Trending 當日新增 star 數，僅供參考，不代表推薦或背書。
#GitHub #開源 #程式設計 #開源專案 #GitHubTrending #軟體開發 #VoiceStudio #Python #AI #語音 #TradingAgents #SEO #Shorts
4 likes · 164 views
I'm back! Here's What's Changing at Binary Tech Labs
Well, it's been a while since I last uploaded to Binary Tech Labs, and I figured it was time to explain where I've been. And for the first time, I'm actually showing my face on camera!
My job as a contract administrator takes me to remote work camps for 21 days at a time, followed by just seven days at home. Between work, family, and everything else, finding time to make smart home and electronics videos became pretty difficult.
But I've missed making videos, and I've decided to take Binary Tech Labs in a slightly different direction.
So, what's changing?
I've been finding some really interesting free and open-source software projects on GitHub. There are plenty of videos showing off what these applications can do, but not nearly enough showing you how to actually install them and get them running.
That's where I want to focus.
Going forward, I'll be exploring open-source software, self-hosted applications, Linux, Docker, and other interesting projects. I'll walk through the installation process, configuration, and troubleshooting when things don't go according to plan.
No skipping the difficult parts. Just practical tutorials showing you how to get things working.
First up is Coolify!
We'll get Coolify installed and running so we have a platform to deploy and experiment with other open-source applications in future videos.
🔗 Coolify: coolify.io
🔗 Coolify on GitHub: coollabsio/coolify
If you've stuck around during my absence, thank you! I really appreciate it.
And if you've come across something interesting on GitHub that you'd like to see installed, let me know in the comments. I'm always looking for new projects to try.
Thanks for watching, and let's get something running!
#BinaryTechLabs #OpenSource #SelfHosting
[de-DE] Ich bin zurück! Das ändert sich bei Binary Tech Labs
Nun, es ist schon eine Weile her, seit ich das letzte Mal etwas auf Binary Tech Labs hochgeladen habe, und ich dachte, es wäre an der Zeit zu erklären, wo ich die ganze Zeit gesteckt habe. Und zum ersten Mal zeige ich mich sogar vor der Kamera!
Mein Job als freiberuflicher Administrator führt mich jeweils 21 Tage am Stück auf Remote-Workcamps, gefolgt von nur sieben Tagen zu Hause. Zwischen Arbeit, Familie und allem anderen wurde es ziemlich schwierig, Zeit für Videos über Smart Home und Elektronik zu finden.
Aber ich habe das Videodrehen vermisst und beschlossen, Binary Tech Labs in eine etwas andere Richtung zu lenken.
Was ändert sich also?
Ich habe einige wirklich interessante kostenlose und Open-Source-Softwareprojekte auf GitHub entdeckt. Es gibt zwar viele Videos, die zeigen, was diese Anwendungen können, aber viel zu wenige, die erklären, wie man sie installiert und zum Laufen bringt.
Darauf möchte ich mich in Zukunft konzentrieren.
Ich werde mich mit Open-Source-Software, selbstgehosteten Anwendungen, Linux, Docker und anderen interessanten Projekten beschäftigen. Ich führe euch durch die Installation, Konfiguration und Fehlerbehebung, falls etwas nicht wie geplant läuft.
Keine Überspringung der schwierigen Teile. Nur praktische Anleitungen, die euch zeigen, wie ihr alles zum Laufen bringt.
Als Erstes: Coolify!
Wir installieren und starten Coolify, damit wir eine Plattform haben, um in zukünftigen Videos andere Open-Source-Anwendungen zu testen und bereitzustellen.
🔗 Coolify: coolify.io
🔗 Coolify auf GitHub: coollabsio/coolify
Vielen Dank, dass ihr während meiner Abwesenheit dabei geblieben seid! Ich weiß das sehr zu schätzen.
Und falls ihr auf GitHub etwas Interessantes entdeckt habt, das ihr gerne installiert sehen würdet, lasst es mich in den Kommentaren wissen. Ich bin immer auf der Suche nach neuen Projekten zum Ausprobieren.
Danke fürs Zuschauen, und los geht's!
#BinaryTechLabs #OpenSource #SelfHosting
[es-US] ¡He vuelto! Estos son los cambios en Binary Tech Labs
Bueno, hacía tiempo que no subía nada a Binary Tech Labs, y pensé que era hora de contarles dónde he estado. ¡Y por primera vez, me muestro en cámara!
Mi trabajo como administrador de contratos me lleva a campamentos de trabajo remotos durante 21 días seguidos, seguidos de solo siete días en casa. Entre el trabajo, la familia y todo lo demás, encontrar tiempo para hacer videos sobre hogares inteligentes y electrónica se volvió bastante difícil.
Pero he echado de menos hacer videos, y he decidido darle un nuevo enfoque a Binary Tech Labs.
¿Qué está cambiando?
He estado descubriendo proyectos de software libre y de código abierto muy interesantes en GitHub. Hay muchos videos que muestran lo que estas aplicaciones pueden hacer, pero no hay suficientes que expliquen cómo instalarlas y ponerlas en marcha.
Ahí es donde quiero centrarme.
De ahora en adelante, exploraré software de código abierto, aplicaciones autoalojadas, Linux, Docker y otros proyectos interesantes. Te guiaré a través del proceso de instalación, configuración y solución de problemas cuando algo no salga según lo planeado.
Sin saltarnos las partes difíciles. Solo tutoriales prácticos que te mostrarán cómo hacer que todo funcione.
¡Empezaremos con Coolify!
Instalaremos y pondremos en marcha Coolify para tener una plataforma donde implementar y experimentar con otras aplicaciones de código abierto en futuros videos.
🔗 Coolify: coolify.io
🔗 Coolify en GitHub: coollabsio/coolify
Si has estado aquí durante mi ausencia, ¡gracias! Lo aprecio mucho.
Y si has encontrado algo interesante en GitHub que te gustaría ver instalado, házmelo saber en los comentarios. Siempre estoy buscando nuevos proyectos para probar.
Gracias por ver el video, ¡y manos a la obra!
#BinaryTechLabs #OpenSource #SelfHosting
[fr-FR] Je suis de retour ! Voici ce qui change chez Binary Tech Labs
Eh bien, ça fait un bail que je n'ai rien publié sur Binary Tech Labs, et je me suis dit qu'il était temps de vous expliquer ce que j'ai fait. Et pour la première fois, je me montre à la caméra !
Mon travail d'administrateur de contrats m'amène à travailler en télétravail pendant 21 jours d'affilée, suivis de seulement sept jours à la maison. Entre le travail, la famille et tout le reste, trouver le temps de faire des vidéos sur la domotique et l'électronique est devenu assez difficile.
Mais les vidéos me manquaient, et j'ai décidé d'orienter Binary Tech Labs vers une direction légèrement différente.
Alors, qu'est-ce qui change ?
J'ai découvert des projets de logiciels libres et open source vraiment intéressants sur GitHub. On trouve plein de vidéos qui montrent ce que ces applications peuvent faire, mais beaucoup moins qui expliquent comment les installer et les faire fonctionner.
C'est là-dessus que je veux me concentrer.
À l'avenir, j'explorerai les logiciels libres, les applications auto-hébergées, Linux, Docker et d'autres projets intéressants. Je vous guiderai pas à pas à travers le processus d'installation, la configuration et le dépannage en cas de problème.
Pas question de passer sous silence les difficultés ! Des tutoriels pratiques pour vous montrer comment tout faire fonctionner.
On commence avec Coolify !
On installera et on lancera Coolify afin d'avoir une plateforme pour déployer et expérimenter d'autres applications open source dans de futures vidéos.
🔗 Coolify : coolify.io
🔗 Coolify sur GitHub : coollabsio/coolify
Merci d'être resté(e) malgré mon absence ! C'est vraiment gentil de votre part.
Et si vous avez trouvé quelque chose d'intéressant sur GitHub que vous aimeriez voir installé, n'hésitez pas à me le dire dans les commentaires. Je suis toujours à la recherche de nouveaux projets à tester.
Merci d'avoir regardé, et c'est parti !
#BinaryTechLabs #OpenSource #SelfHosting
[hi] मैं वापस आ गया हूँ! Binary Tech Labs में क्या बदलाव हो रहे हैं, यहाँ देखें
बाइनरी टेक लैब्स पर वीडियो अपलोड किए हुए काफी समय हो गया है, और मैंने सोचा कि अब बताने का समय आ गया है कि मैं कहाँ था। और पहली बार, मैं कैमरे पर अपना चेहरा दिखा रहा हूँ!
एक कॉन्ट्रैक्ट एडमिनिस्ट्रेटर के तौर पर मेरी नौकरी के चलते मुझे 21 दिनों के लिए रिमोट वर्क कैंप में जाना पड़ता है, जिसके बाद मुझे सिर्फ सात दिन घर पर बिताने को मिलते हैं। काम, परिवार और बाकी सब चीज़ों के बीच, स्मार्ट होम और इलेक्ट्रॉनिक्स से जुड़े वीडियो बनाने के लिए समय निकालना काफी मुश्किल हो गया था।
लेकिन मुझे वीडियो बनाने की बहुत याद आ रही थी, और मैंने बाइनरी टेक लैब्स को थोड़ा अलग दिशा देने का फैसला किया है।
तो, क्या बदल रहा है?
मुझे GitHub पर कुछ बेहद दिलचस्प फ्री और ओपन-सोर्स सॉफ्टवेयर प्रोजेक्ट्स मिले हैं। इन एप्लीकेशन्स की क्षमताओं को दिखाने वाले कई वीडियो तो हैं, लेकिन इन्हें इंस्टॉल करने और चलाने का तरीका बताने वाले वीडियो बहुत कम हैं।
यहीं पर मैं ध्यान देना चाहता हूँ।
आगे चलकर, मैं ओपन-सोर्स सॉफ्टवेयर, सेल्फ-होस्टेड एप्लीकेशन्स, लिनक्स, डॉकर और अन्य दिलचस्प प्रोजेक्ट्स पर काम करूँगा। मैं आपको इंस्टॉलेशन प्रक्रिया, कॉन्फ़िगरेशन और समस्या निवारण के बारे में विस्तार से बताऊंगा, खासकर तब जब चीजें योजना के अनुसार न हों।
मुश्किल हिस्सों को छोड़ा नहीं जाएगा। ये सिर्फ़ व्यावहारिक ट्यूटोरियल होंगे जो आपको दिखाएंगे कि चीज़ों को कैसे काम में लाया जाए।
सबसे पहले है Coolify!
हम Coolify को इंस्टॉल और रन करेंगे ताकि भविष्य के वीडियो में हम अन्य ओपन-सोर्स एप्लिकेशन को डिप्लॉय और एक्सपेरिमेंट करने के लिए एक प्लेटफ़ॉर्म बना सकें।
🔗 Coolify: coolify.io
🔗 Coolify GitHub पर: coollabsio/coolify
अगर आप मेरी अनुपस्थिति के दौरान भी बने रहे, तो धन्यवाद! मैं वास्तव में इसकी सराहना करता हूँ।
और अगर आपको GitHub पर कुछ दिलचस्प मिला है जिसे आप इंस्टॉल होते देखना चाहते हैं, तो मुझे कमेंट्स में बताएं। मैं हमेशा नए प्रोजेक्ट्स की तलाश में रहता हूँ।
देखने के लिए धन्यवाद, और चलिए कुछ शुरू करते हैं!
#BinaryTechLabs #OpenSource #SelfHosting
[id] Saya Kembali! Inilah Perubahan yang Terjadi di Binary Tech Labs
Baiklah, sudah cukup lama sejak terakhir kali saya mengunggah video ke Binary Tech Labs, dan saya rasa sudah waktunya untuk menjelaskan ke mana saya pergi. Dan untuk pertama kalinya, saya benar-benar menunjukkan wajah saya di kamera!
Pekerjaan saya sebagai administrator kontrak membawa saya ke kamp kerja jarak jauh selama 21 hari berturut-turut, diikuti hanya tujuh hari di rumah. Di antara pekerjaan, keluarga, dan segalanya, menemukan waktu untuk membuat video tentang rumah pintar dan elektronik menjadi cukup sulit.
Tapi saya rindu membuat video, dan saya memutuskan untuk membawa Binary Tech Labs ke arah yang sedikit berbeda.
Jadi, apa yang berubah?
Saya telah menemukan beberapa proyek perangkat lunak sumber terbuka dan gratis yang sangat menarik di GitHub. Ada banyak video yang menunjukkan apa yang dapat dilakukan aplikasi ini, tetapi tidak cukup banyak yang menunjukkan cara menginstalnya dan menjalankannya.
Di situlah saya ingin fokus.
Ke depannya, saya akan mengeksplorasi perangkat lunak sumber terbuka, aplikasi yang dihosting sendiri, Linux, Docker, dan proyek-proyek menarik lainnya. Saya akan memandu proses instalasi, konfigurasi, dan pemecahan masalah ketika ada hal-hal yang tidak berjalan sesuai rencana.
Tidak ada bagian yang sulit yang akan dilewati. Hanya tutorial praktis yang menunjukkan cara agar semuanya berfungsi.
Yang pertama adalah Coolify!
Kita akan menginstal dan menjalankan Coolify sehingga kita memiliki platform untuk menyebarkan dan bereksperimen dengan aplikasi open-source lainnya di video mendatang.
🔗 Coolify: coolify.io
🔗 Coolify di GitHub: coollabsio/coolify
Jika Anda tetap setia selama ketidakhadiran saya, terima kasih! Saya sangat menghargai itu.
Dan jika Anda menemukan sesuatu yang menarik di GitHub yang ingin Anda lihat diinstal, beri tahu saya di kolom komentar. Saya selalu mencari proyek baru untuk dicoba.
Terima kasih telah menonton, dan mari kita mulai!
#BinaryTechLabs #OpenSource #SelfHosting
[it] Sono tornato! Ecco cosa cambia a Binary Tech Labs
Beh, è passato un po' di tempo dall'ultimo video che ho caricato su Binary Tech Labs, e ho pensato che fosse ora di spiegare dove sono stato. E per la prima volta, mi mostro anche in video!
Il mio lavoro come amministratore di contratti mi porta in campi di lavoro remoti per 21 giorni di fila, seguiti da soli sette giorni a casa. Tra lavoro, famiglia e tutto il resto, trovare il tempo per realizzare video su domotica ed elettronica è diventato piuttosto difficile.
Ma mi mancava fare video, e ho deciso di dare a Binary Tech Labs una direzione leggermente diversa.
Quindi, cosa cambierà?
Ho scoperto alcuni progetti software gratuiti e open source davvero interessanti su GitHub. Ci sono molti video che mostrano cosa possono fare queste applicazioni, ma non abbastanza che mostrano come installarle e farle funzionare.
È su questo che voglio concentrarmi.
D'ora in poi, esplorerò software open source, applicazioni self-hosted, Linux, Docker e altri progetti interessanti. Vi guiderò attraverso il processo di installazione, configurazione e risoluzione dei problemi nel caso in cui qualcosa non vada come previsto.
Non salterò le parti più difficili. Solo tutorial pratici che vi mostreranno come far funzionare tutto.
Per cominciare, Coolify!
Installeremo e avvieremo Coolify in modo da avere una piattaforma su cui implementare e sperimentare altre applicazioni open source nei video futuri.
🔗 Coolify: coolify.io
🔗 Coolify su GitHub: coollabsio/coolify
Se siete rimasti con me durante la mia assenza, grazie! Lo apprezzo davvero.
E se avete trovato qualcosa di interessante su GitHub che vorreste vedere installato, fatemelo sapere nei commenti. Sono sempre alla ricerca di nuovi progetti da provare.
Grazie per aver guardato, e iniziamo!
#BinaryTechLabs #OpenSource #SelfHosting
[pt-BR] Voltei! Confira o que está mudando na Binary Tech Labs
Bem, já faz um tempo desde que publiquei meu último vídeo no Binary Tech Labs, e achei que era hora de explicar por onde andei. E, pela primeira vez, estou mostrando meu rosto na câmera!
Meu trabalho como administrador de contratos me leva a acampamentos de trabalho remoto por 21 dias seguidos, seguidos por apenas sete dias em casa. Entre trabalho, família e tudo mais, encontrar tempo para fazer vídeos sobre casas inteligentes e eletrônicos ficou bem difícil.
Mas eu estava com saudades de fazer vídeos e decidi dar um rumo um pouco diferente ao Binary Tech Labs.
Então, o que está mudando?
Tenho encontrado alguns projetos de software livre e de código aberto muito interessantes no GitHub. Há muitos vídeos mostrando o que esses aplicativos podem fazer, mas não o suficiente mostrando como instalá-los e executá-los.
É nisso que quero me concentrar.
Daqui para frente, explorarei software de código aberto, aplicativos auto-hospedados, Linux, Docker e outros projetos interessantes. Neste vídeo, vou mostrar o processo de instalação, configuração e solução de problemas quando algo não sair como planejado.
Sem pular as partes difíceis. Apenas tutoriais práticos mostrando como fazer tudo funcionar.
Primeiro, vamos usar o Coolify!
Vamos instalar e executar o Coolify para termos uma plataforma para implantar e experimentar outros aplicativos de código aberto em vídeos futuros.
🔗 Coolify: coolify.io
🔗 Coolify no GitHub: coollabsio/coolify
Se você continuou acompanhando durante minha ausência, muito obrigado! Agradeço de verdade.
E se você encontrou algo interessante no GitHub que gostaria de ver instalado, deixe um comentário. Estou sempre procurando novos projetos para testar.
Obrigado por assistir e vamos colocar algo em funcionamento!
#BinaryTechLabs #OpenSource #SelfHosting
2 likes · 93 views
自己有 VPS 的独立开发者，可以研究下 Coolify。
开源、自部署，支持从 GitHub 部署应用、自动 HTTPS、数据库和 Docker 服务管理。
比每次手写部署脚本省事不少。
注意软件免费，服务器还是自己付钱。
coollabsio/coolify
5 likes · 1,158 views
Coolify: 70,210 titles against 3 fingerprints, and the port that explains the gap
Coolify: 70,210 titles against 3 fingerprints, and the port that explains the gap
Self-hosted platforms that deploy other software hold deploy keys, environment variables, and database passwords. Coolify is one of them, and its public footprint on 23 October 2026 produced the most unusual set of numbers in this batch.
The three measurements
ZoomEye returned 70,210 matches for title="Coolify", 3 matches for app="Coolify", and 66,831 matches for title="Coolify" && port="8000".
The application fingerprint number is almost useless: three is too small to describe anything, and it suggests the scanner has no stable response signature for the product. The title number is large. The port-constrained number is nearly as large.
That last relationship is the finding. Ninety-five percent of the title matches sit on port 8000, which is the port Coolify's own installation documentation assigns to its dashboard.
Why that co-occurrence matters
When a product name appears in a page title, the match usually includes documentation, blog posts, and project pages. Those live on 443 or 80, served by a normal web host. They do not live on port 8000.
A population where the title string and the dashboard port coincide at 95 percent is a population of running consoles rather than a population of articles about the product. That is a defensible inference, and it is the kind of inference a count alone will never give you.
It does not follow that 66,831 Coolify servers are exposed and exploitable. It follows that the number is much closer to an installation count than a title count normally is.
What a Coolify dashboard controls
Coolify deploys applications to servers. To do that it stores credentials for the target servers, the source repositories, the container registry, and the environment of every deployed service. The dashboard is the interface to that store.
The architecture decision that matters is how the dashboard talks to the target machines. A Coolify instance that holds SSH keys for a fleet of servers is a single point of compromise for that fleet. A deployment where the same instance is reachable from the internet without a network restriction is a single point of compromise with a public address.
Coolify's own documentation covers securing the dashboard, and the interesting question for an operator is not whether the product has a security feature but whether it was configured before the first deploy.
Turning the number into a decision
The count gives three options. If you do not run Coolify, the number is context: a large installed base with a predictable port means automated scanning against it is worth someone's time. If you run one instance, the check is whether port 8000 is reachable from the internet at all, and whether the account holding the deploy keys is separate from the account you use daily. If you run several, the question becomes whether they share credentials, because shared credentials across instances turn one compromise into a fleet compromise.
The port observation also gives a cheap external check that does not require authentication. A host answering on port 8000 with a Coolify title is presenting the dashboard. Whether it then requires a login, a second factor, or nothing at all is visible only in a browser, which is the boundary between what this article can state and what only you can test on your own systems.
The measurement lesson, stated carefully
Three fingerprints and 70,210 titles is not a contradiction. It is a fingerprinting gap on one side and a string match on the other, joined by a port constraint that happens to be unusually informative.
Report the numbers with their queries and the collection date. Say that the port co-occurrence is consistent with running dashboards. Avoid saying that the hosts are unsecured, because nothing in the data supports that, and avoid the opposite claim that the number is meaningless, because the port correlation is evidence.
Practical actions
Move the dashboard off the default port and behind a proxy that enforces authentication and source restrictions. That single change moves a host out of this dataset and out of most automated scans.
Separate the credentials. A Coolify instance should not use a deploy key that also grants access to unrelated infrastructure, and the target servers should accept that key only for the operations Coolify performs.
Log the dashboard's authentication events and review them for attempts that succeed after a burst of failures. A public dashboard on a predictable port receives that traffic continuously, and the one success that matters is easy to lose in it.
References
- Coolify installation documentation, coolify.io
- Coolify project repository, coollabsio/coolify
- ZoomEye AI query results collected 23 October 2026 for title="Coolify", app="Coolify", and title="Coolify" && port="8000", sub-type all
Mentions
Coolify vs Railway and Render: what self-hosting really costs > TL;DR > > - What you get: a side-by-side monthly bill for one small web app plus Postgres on Coolify (self-hosted and Cloud), Railway, Render and Hubfly space, plus a worksheet for the hours self-hosting takes. > - Who it's for: developers and small teams deciding between "my own server with Coolify" and "a platform that runs it for me". > - Time to read: 10 minutes. Prices checked on 4 November 2026. > - Short answer: for one or two small apps, a managed platform is usually cheaper _and_ less work. Coolify starts to win at roughly 5 to 12 small apps on one server, depending on whether they share a database and how much memory they need, if you're happy owning backups and updates. Your Railway or Render bill keeps creeping up, and Coolify looks like a free way out. You rent a server, run one install command, and get Git deploys, databases and HTTPS in a nice dashboard. No platform bill. But the server isn't free, the backups aren't automatic until you set them up, and nobody patches it for you. This guide puts real numbers on both sides, so you can pick the option that costs you less in money _and_ in evenings. Try it on Hubfly space: the free tier gives you 360 hours a month, no card needed. What Coolify is (and why people love it) Coolify is an open-source, self-hostable platform. You connect your own servers and it handles Git deploys, Docker images, Compose stacks, one-click services and databases. It's a good piece of software, and it wins on several things: - No platform fee if you self-host. The self-hosted edition is "Free forever" with every feature, per Coolify's pricing page. - Many apps on one bill. You pay for the server, not per app. Ten tiny apps can share one box. - Real database backups. Coolify can schedule backups for PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse and SQLite, and upload a copy to any S3-compatible storage (backups docs). - Portability. It runs on almost any Linux box: a VPS, a dedicated server, even a Raspberry Pi. - No lock-in. Your apps are plain Docker containers on a machine you control. If you already run Linux servers for a living, Coolify is a great tool. The question is what it costs everyone else. The two ways to run Coolify Self-hosted. You install Coolify on your own server. The install guide asks for at least 2 CPU cores, 2 GB RAM and 10 GB of disk, on a supported Linux distribution, with SSH access and the right firewall ports open. Then you run one script. Coolify Cloud. The Coolify team runs the dashboard for you. It costs $5 a month for up to 2 connected servers, plus $3 a month for each extra server, and you still bring and pay for your own servers (pricing). The upside: the control plane's updates and backups are managed, and your server only needs room for your apps. Either way, the server running your apps is still yours to look after. The reference app Whether you're weighing Coolify vs Railway or Render, every option below runs the same small setup: - One web app, always on, about 512 MB of memory. - One small Postgres database. - Low traffic: a side project, an internal tool or an early-stage SaaS. Bandwidth is left out because the plans bundle it very differently. Check it separately if you serve a lot of files or video. The monthly bill, side by side Prices from each vendor's official page on 4 November 2026, in US dollars, before tax. | Option | What you pay for | Monthly cost | Backups included in that price? | | --- | --- | --- | --- | | Coolify self-hosted on a DigitalOcean Droplet (2 vCPU, 2 GiB, $18) | Server + weekly server backups (20% of Droplet price) | $21.60 | Weekly server image. Database dumps to S3 are free to set up in Coolify, plus storage cost | | Coolify Cloud + a 1 vCPU / 2 GiB Droplet ($12) | $5 Coolify Cloud + server + weekly backups | $19.40 | Same as above; Coolify itself is backed up for you | | Railway Hobby | $5 plan that includes $5 of usage, then usage | about $10.81 (see math below) | Built-in database and volume backups are listed on the pricing page; check which plans include them | | Render | $7 web service (512 MB) + $6 Postgres (256 MB) | $13.00 | Yes: logical backups on paid Postgres instances, plus point-in-time recovery (window depends on your workspace plan) | | Hubfly space | Dedicated container (0.5 vCPU, 512 MB, always on) + Managed Postgres Nano | $4.26 | No automatic database backups yet. Use manual exports | A few honest notes on that table: - Railway bills measured usage, so a busier app costs more. Hubfly space bills the CPU and memory you allocate per hour, so its bill changes only when you resize or add containers. Render, Droplets and Coolify Cloud are fixed monthly plans. - Render also offers up to $10K in migration credits for teams moving production workloads (pricing page). That can matter more than a few dollars a month. - Hubfly space's database has no automatic backups or point-in-time recovery today. Its pricing docs say automatic backups are "coming soon" and point you to manual exports. On that one point, Coolify's scheduled S3 backups are ahead. !The cost panel for a 1 vCPU, 1 GB always-on container: $4.42 a month _The Create Container cost panel shows the monthly price before you deploy. Here: 1 vCPU and 1 GB, always on._ How the numbers are calculated You can redo every line yourself. Months are 730 hours. Hubfly space (rates from the pricing page: CPU $0.004 per vCPU-hour, RAM $0.002 per GB-hour, storage $0.00001536 per GB-hour): - Web container, 0.5 vCPU / 512 MB / 4 GB disk, always on: 0.5 × 0.004 × 730 = $1.46, plus 0.5 × 0.002 × 730 = $0.73, plus 4 × 0.00001536 × 730 = $0.04. Total $2.23. - Managed Postgres Nano (0.25 vCPU, 512 MiB, 10 GiB), from the database pricing docs: compute $0.002 per hour + system disk $0.00001536 + 30% management fee $0.0006 + storage $0.0001536 = $0.00276896 per hour. About $2.02 a month. - Together: $4.26. Want a full vCPU and 1 GB for the web app instead? That container is $4.42 (screenshot above), so the total is $6.44. Railway (rates from the pricing page): $0.00000772 per vCPU-second ($20.29 per vCPU-month), $0.00000386 per GB-second ($10.14 per GB-month), volumes $0.00000006 per GB-second ($0.16 per GB-month). Railway bills what your app actually uses, so the bill depends on load. Assume: - Web app averages 0.1 vCPU and 512 MB: 0.1 × 20.29 + 0.5 × 10.14 = $7.10. - Postgres averages 0.05 vCPU, 256 MB and a 1 GB volume: 0.05 × 20.29 + 0.25 × 10.14 + 0.16 = $3.71. - Usage $10.81. The $5 Hobby plan includes $5 of usage, so the bill is about $10.81. Render: $7 (web service, 512 MB) + $6 (smallest paid Postgres, 256 MB) = $13, on the free Hobby workspace. Coolify self-hosted: the smallest Droplet that meets Coolify's 2-core, 2 GB minimum is 2 vCPU / 2 GiB at $18. Weekly Droplet backups cost 20% of the Droplet price ($3.60). Total $21.60. Daily backups are 30% ($5.40), for $23.40. Coolify Cloud: $5 + a 1 vCPU / 2 GiB Droplet at $12 + 20% weekly backups ($2.40) = $19.40. Coolify's own docs often suggest Hetzner, which is usually cheaper than DigitalOcean. On 4 November 2026, though, Hetzner's Regular Performance page listed its plans as "currently unavailable", so it isn't in the table. If you can get a Hetzner server, redo the Coolify rows with its price. The cost nobody puts in the table: your hours A platform bill is only half the price. With self-hosted Coolify you also own: 1. The server. OS updates, SSH keys, firewall rules, disk space. Docker images and old builds fill disks quietly. 2. Coolify itself. You can turn on automatic updates, which install new releases on a schedule (daily at midnight by default, per the update docs). The dashboard restarts briefly during an update, and the docs advise taking an instance backup and reading the release notes first. 3. Security. Coolify's automated install needs root access to your server, so its bugs matter. Its GitHub repository lists 70 published security advisories as of 4 November 2026. Publishing them openly is a good sign, but someone on your team needs to read them and update promptly. 4. The first-login race. The install guide warns that whoever reaches the registration page first becomes the admin, with root access to your server. Create your admin account right away, or pre-create it with the install variables. 5. Backups and restores. Coolify's own docs say it plainly: "A backup is not a restore test." You need an S3 bucket, a schedule, a retention rule and an occasional practice restore. 6. Outages. One server means one point of failure. When it goes down at 2 a.m., you're the on-call team. A worksheet for your own time Use these as starting estimates and adjust them to your experience. | Task | First month | Each month after | | --- | --- | --- | | Create server, SSH, firewall, DNS, install Coolify | 2–4 h | – | | Set up S3 backups and do one practice restore | 1–2 h | 0.5 h (restore test) | | OS and Coolify updates, advisories, disk cleanup | – | 0.5–1 h | | Something breaks | – | 0–2 h | | Total | 3–6 h | 1–3.5 h | Multiply the monthly hours by what an hour of your time is worth. At $30 an hour, even 1 hour a month adds $30, more than the whole self-hosted server bill. That's the real comparison. If you enjoy running servers, or you're learning, those hours aren't a cost. They're the point. That's a perfectly good reason to choose Coolify. When Coolify wins on money: many small apps on one server The managed rows grow with every app. The self-hosted row is flat until the server is full. Using the numbers above (a $21.60 Droplet with backups vs $2.23 per always-on Hubfly space container): | Small apps | Hubfly space, all sharing one Nano Postgres | Hubfly space, each with its own Nano Postgres | Coolify, 2 GiB Droplet + backups | Coolify, 4 GiB Droplet + backups | | --- | --- | --- | --- | --- | | 1 | $4.26 | $4.26 | $21.60 | $28.80 | | 3 | $8.73 | $12.77 | $21.60 | $28.80 | | 5 | $13.20 | $21.28 | $21.60 | $28.80 | | 7 | $17.67 | $29.79 | $21.60 | $28.80 | | 9 | $22.14 | $38.31 | $21.60 | $28.80 | | 12 | $28.84 | $51.07 | $21.60 | $28.80 | On the smallest server Coolify supports, it breaks even at about 5 apps that each need their own database, or about 9 apps sharing one. Size the server for that many apps (4 GiB) and the break-even moves to about 7 and 12. Two caveats keep this fair: - The apps share 2 vCPUs and 2 GB on the Droplet, and Coolify uses some of that itself. Nine always-on 512 MB containers on Hubfly space get 4.5 vCPUs and 4.5 GB between them; nine 512 MB apps won't fit in 2 GB next to Coolify. In practice, budget a 4 GiB Droplet ($24, or $28.80 with weekly backups) for that many apps, which moves the break-even point further out. - Staging and hobby apps don't need to run all night. With Auto Sleep on, a 0.5 vCPU / 512 MB Hubfly space container shows $1.14 a month in the cost panel, which pushes the break-even point further out. Which should you pick? Pick Coolify self-hosted if: - You run several small apps (about 5–7 if each needs its own database, about 9–12 if they share one, depending on server size) and want one flat bill. - You already maintain Linux servers, or you want to learn. - You need full control over where data lives, or to run on hardware you own. - You'll actually set up S3 backups and test a restore. Pick Coolify Cloud if: you like Coolify's workflow and own servers, but don't want to babysit the dashboard itself. Pick Railway or Render if: you want an established managed platform, you rely on one of its specific features, and the bill fits. Render's migration credits can make a move nearly free for a larger team. Pick Hubfly space if: you want managed containers with the lowest bill in this comparison for one or two small apps, a price you can see before you deploy, and a monthly budget cap per project. Just plan your own database exports until automatic backups ship. !Project budget cap set to $10, with the projected monthly cost shown _A project budget cap sets a hard monthly limit for the project, with emails at 80% and 90%, so a mistake can't run up a surprise bill._ What can go wrong 1. "My Coolify server ran out of disk." Old images, build caches and local backups pile up under /data/coolify and Docker's own folders. Set backup retention in Coolify, upload backups to S3 with "Delete after S3 upload", and prune unused images on a schedule. 2. "My backup job says Success but I can't restore." A file existing isn't proof it restores. Restore into a throwaway database once a month and point a copy of your app at it. 3. "My managed bill is higher than the table." Usage-billed platforms charge for what you actually run. A bigger instance, a second replica or a chatty worker changes the math. Check each platform's cost estimate before deploying, and set a spending cap where the platform offers one. Try the managed side in a few minutes Deploying a container image on Hubfly space is short: 1. Create a project and pick a region. Set a monthly budget cap under Advanced Options if you want a hard limit. 2. Click Create → Create Container, choose Docker image, and enter your image, like your-org/your-app:1.0. 3. On Resources, choose Dedicated Tier, set CPU and memory, and turn Auto Sleep off for an always-on app. The cost panel updates as you move the sliders. 4. Click Deploy Container. A small image is running in well under a minute. 5. Open Network → Add Domain → Auto Endpoint and pick your port. You get an HTTPS address like your-app.eu1.hubfly.app, about a minute after clicking Deploy for a small image. !A dedicated container running, with 1 vCPU and 1 GB _The container page after deploy: status, tier and resources at a glance._ !The Network tab with an HTTPS subdomain routed to port 80 _Network → Add Domain creates an HTTPS subdomain with TLS on by default._ For the database, create a Managed service project, choose PostgreSQL and the Nano size, and copy the connection string into your app's environment variables. See how to get a managed PostgreSQL database for about $2 a month. Takeaway Coolify is free software, not free hosting. For one or two small apps, a managed platform is often cheaper than the server Coolify needs, before you count a single hour of your time. Once you run roughly 5–7 small apps that each need their own database (or 9–12 that share one), and you're comfortable owning backups and updates, Coolify on one server becomes the cheaper, flexible choice. Read next: - Fixed vs pay-as-you-go hosting: find your break-even point - Best Heroku alternatives in 2026: 7 options and what they cost - Deploy a docker-compose.yml as-is: 8 platforms compared Go further on Hubfly space - Moving from Railway? Follow how to move your app from Railway to Hubfly space, step by step. - Store backups and files in Hubfly space Storage, S3-compatible buckets at about $0.011 per GB-month. A Coolify backup bucket works too. - Deploy on every push with GitHub Actions and a deploy webhook. Run the numbers for your own app with the Hubfly space pricing calculator, or start free on Hubfly space: 360 hours a month, no card needed.
I open-sourced Coolify. coollabsio/coolify Now @heyandras fears me.
Shoutrrr: alternative to Buffer Essentials ($60/yr) #Shorts A self-hosted social media scheduler: write a post once, send it to several networks at the same time, or queue it on a schedule. The pairing is the project's own: the README calls it an open-source alternative to Buffer, Typefully and Hootsuite. It publishes to X, Bluesky, LinkedIn, Facebook Pages, Instagram, Threads and Discord, splits long posts into threads where a network allows it, and tracks followers and engagement. Buffer charges per channel, so sixty dollars is the saving for one, every extra channel adds to it, and this is another item that is not an AI tool. Replaces Buffer Essentials at $60 a year (one channel, billed yearly; $5/mo monthly). The catch: You run it on your own server and register your own developer apps with X, LinkedIn and Meta. LinkedIn analytics do not work for personal accounts, and Buffer's free plan already covers three channels. Apache-2.0 licence, 471 GitHub stars (checked 2026-10-28). coollabsio/shoutrrr Full episode: youtu.be #FUBARAI
yesss @coolify.io v4.5.0 introduced passkeys github.com/coollabsio/coolify/releases/tag/v4.5.0
Coolify : un PaaS auto-hébergeable, alternative Open Source à Vercel, Heroku et Netlify. Il permet de déployer des sites statiques, des bases de données, des applications et plus de 360 services en un clic, sur vos propres serveurs 👉 coollabsio/coolify t.co
Coolify : un PaaS auto-hébergeable, alternative Open Source à Vercel, Heroku et Netlify. Il permet de déployer des sites statiques, des bases de données, des applications et plus de 360 services en un clic, sur vos propres serveurs 👉 coollabsio/coolify
不用雲端也能克隆聲音， VoiceStudio 支援 646 語言做影片配音 今天 GitHub 熱榜，VoiceStudio 一天狂噴 1,592 顆星。TradingAgents、claude-seo、coolify、thinkrail 也上榜。VoiceStudio 是免本地 ElevenLabs 替代，646 語言。TradingAgents 多 agent 交易框架。claude-seo 審網站。coolify 自架 PaaS。thinkrail Vibe IDE。 1｜VoiceStudio：免本地語音 debpalash/VoiceStudio 2｜TradingAgents：AI 交易 TauricResearch/TradingAgents 3｜claude-seo：SEO 神技 AgriciDaniel/claude-seo 4｜coolify：自架 PaaS coollabsio/coolify 5｜thinkrail：Vibe IDE JetBrains/thinkrail 資料來源：GitHub Trending（今日新增 star） 每天幫你篩一遍 GitHub 開源熱榜。 排名依 GitHub Trending 當日新增 star 數，僅供參考，不代表推薦或背書。 #GitHub #開源 #程式設計 #開源專案 #GitHubTrending #軟體開發 #VoiceStudio #Python #AI #語音 #TradingAgents #SEO #Shorts
I'm back! Here's What's Changing at Binary Tech Labs Well, it's been a while since I last uploaded to Binary Tech Labs, and I figured it was time to explain where I've been. And for the first time, I'm actually showing my face on camera! My job as a contract administrator takes me to remote work camps for 21 days at a time, followed by just seven days at home. Between work, family, and everything else, finding time to make smart home and electronics videos became pretty difficult. But I've missed making videos, and I've decided to take Binary Tech Labs in a slightly different direction. So, what's changing? I've been finding some really interesting free and open-source software projects on GitHub. There are plenty of videos showing off what these applications can do, but not nearly enough showing you how to actually install them and get them running. That's where I want to focus. Going forward, I'll be exploring open-source software, self-hosted applications, Linux, Docker, and other interesting projects. I'll walk through the installation process, configuration, and troubleshooting when things don't go according to plan. No skipping the difficult parts. Just practical tutorials showing you how to get things working. First up is Coolify! We'll get Coolify installed and running so we have a platform to deploy and experiment with other open-source applications in future videos. 🔗 Coolify: coolify.io 🔗 Coolify on GitHub: coollabsio/coolify If you've stuck around during my absence, thank you! I really appreciate it. And if you've come across something interesting on GitHub that you'd like to see installed, let me know in the comments. I'm always looking for new projects to try. Thanks for watching, and let's get something running! #BinaryTechLabs #OpenSource #SelfHosting [de-DE] Ich bin zurück! Das ändert sich bei Binary Tech Labs Nun, es ist schon eine Weile her, seit ich das letzte Mal etwas auf Binary Tech Labs hochgeladen habe, und ich dachte, es wäre an der Zeit zu erklären, wo ich die ganze Zeit gesteckt habe. Und zum ersten Mal zeige ich mich sogar vor der Kamera! Mein Job als freiberuflicher Administrator führt mich jeweils 21 Tage am Stück auf Remote-Workcamps, gefolgt von nur sieben Tagen zu Hause. Zwischen Arbeit, Familie und allem anderen wurde es ziemlich schwierig, Zeit für Videos über Smart Home und Elektronik zu finden. Aber ich habe das Videodrehen vermisst und beschlossen, Binary Tech Labs in eine etwas andere Richtung zu lenken. Was ändert sich also? Ich habe einige wirklich interessante kostenlose und Open-Source-Softwareprojekte auf GitHub entdeckt. Es gibt zwar viele Videos, die zeigen, was diese Anwendungen können, aber viel zu wenige, die erklären, wie man sie installiert und zum Laufen bringt. Darauf möchte ich mich in Zukunft konzentrieren. Ich werde mich mit Open-Source-Software, selbstgehosteten Anwendungen, Linux, Docker und anderen interessanten Projekten beschäftigen. Ich führe euch durch die Installation, Konfiguration und Fehlerbehebung, falls etwas nicht wie geplant läuft. Keine Überspringung der schwierigen Teile. Nur praktische Anleitungen, die euch zeigen, wie ihr alles zum Laufen bringt. Als Erstes: Coolify! Wir installieren und starten Coolify, damit wir eine Plattform haben, um in zukünftigen Videos andere Open-Source-Anwendungen zu testen und bereitzustellen. 🔗 Coolify: coolify.io 🔗 Coolify auf GitHub: coollabsio/coolify Vielen Dank, dass ihr während meiner Abwesenheit dabei geblieben seid! Ich weiß das sehr zu schätzen. Und falls ihr auf GitHub etwas Interessantes entdeckt habt, das ihr gerne installiert sehen würdet, lasst es mich in den Kommentaren wissen. Ich bin immer auf der Suche nach neuen Projekten zum Ausprobieren. Danke fürs Zuschauen, und los geht's! #BinaryTechLabs #OpenSource #SelfHosting [es-US] ¡He vuelto! Estos son los cambios en Binary Tech Labs Bueno, hacía tiempo que no subía nada a Binary Tech Labs, y pensé que era hora de contarles dónde he estado. ¡Y por primera vez, me muestro en cámara! Mi trabajo como administrador de contratos me lleva a campamentos de trabajo remotos durante 21 días seguidos, seguidos de solo siete días en casa. Entre el trabajo, la familia y todo lo demás, encontrar tiempo para hacer videos sobre hogares inteligentes y electrónica se volvió bastante difícil. Pero he echado de menos hacer videos, y he decidido darle un nuevo enfoque a Binary Tech Labs. ¿Qué está cambiando? He estado descubriendo proyectos de software libre y de código abierto muy interesantes en GitHub. Hay muchos videos que muestran lo que estas aplicaciones pueden hacer, pero no hay suficientes que expliquen cómo instalarlas y ponerlas en marcha. Ahí es donde quiero centrarme. De ahora en adelante, exploraré software de código abierto, aplicaciones autoalojadas, Linux, Docker y otros proyectos interesantes. Te guiaré a través del proceso de instalación, configuración y solución de problemas cuando algo no salga según lo planeado. Sin saltarnos las partes difíciles. Solo tutoriales prácticos que te mostrarán cómo hacer que todo funcione. ¡Empezaremos con Coolify! Instalaremos y pondremos en marcha Coolify para tener una plataforma donde implementar y experimentar con otras aplicaciones de código abierto en futuros videos. 🔗 Coolify: coolify.io 🔗 Coolify en GitHub: coollabsio/coolify Si has estado aquí durante mi ausencia, ¡gracias! Lo aprecio mucho. Y si has encontrado algo interesante en GitHub que te gustaría ver instalado, házmelo saber en los comentarios. Siempre estoy buscando nuevos proyectos para probar. Gracias por ver el video, ¡y manos a la obra! #BinaryTechLabs #OpenSource #SelfHosting [fr-FR] Je suis de retour ! Voici ce qui change chez Binary Tech Labs Eh bien, ça fait un bail que je n'ai rien publié sur Binary Tech Labs, et je me suis dit qu'il était temps de vous expliquer ce que j'ai fait. Et pour la première fois, je me montre à la caméra ! Mon travail d'administrateur de contrats m'amène à travailler en télétravail pendant 21 jours d'affilée, suivis de seulement sept jours à la maison. Entre le travail, la famille et tout le reste, trouver le temps de faire des vidéos sur la domotique et l'électronique est devenu assez difficile. Mais les vidéos me manquaient, et j'ai décidé d'orienter Binary Tech Labs vers une direction légèrement différente. Alors, qu'est-ce qui change ? J'ai découvert des projets de logiciels libres et open source vraiment intéressants sur GitHub. On trouve plein de vidéos qui montrent ce que ces applications peuvent faire, mais beaucoup moins qui expliquent comment les installer et les faire fonctionner. C'est là-dessus que je veux me concentrer. À l'avenir, j'explorerai les logiciels libres, les applications auto-hébergées, Linux, Docker et d'autres projets intéressants. Je vous guiderai pas à pas à travers le processus d'installation, la configuration et le dépannage en cas de problème. Pas question de passer sous silence les difficultés ! Des tutoriels pratiques pour vous montrer comment tout faire fonctionner. On commence avec Coolify ! On installera et on lancera Coolify afin d'avoir une plateforme pour déployer et expérimenter d'autres applications open source dans de futures vidéos. 🔗 Coolify : coolify.io 🔗 Coolify sur GitHub : coollabsio/coolify Merci d'être resté(e) malgré mon absence ! C'est vraiment gentil de votre part. Et si vous avez trouvé quelque chose d'intéressant sur GitHub que vous aimeriez voir installé, n'hésitez pas à me le dire dans les commentaires. Je suis toujours à la recherche de nouveaux projets à tester. Merci d'avoir regardé, et c'est parti ! #BinaryTechLabs #OpenSource #SelfHosting [hi] मैं वापस आ गया हूँ! Binary Tech Labs में क्या बदलाव हो रहे हैं, यहाँ देखें बाइनरी टेक लैब्स पर वीडियो अपलोड किए हुए काफी समय हो गया है, और मैंने सोचा कि अब बताने का समय आ गया है कि मैं कहाँ था। और पहली बार, मैं कैमरे पर अपना चेहरा दिखा रहा हूँ! एक कॉन्ट्रैक्ट एडमिनिस्ट्रेटर के तौर पर मेरी नौकरी के चलते मुझे 21 दिनों के लिए रिमोट वर्क कैंप में जाना पड़ता है, जिसके बाद मुझे सिर्फ सात दिन घर पर बिताने को मिलते हैं। काम, परिवार और बाकी सब चीज़ों के बीच, स्मार्ट होम और इलेक्ट्रॉनिक्स से जुड़े वीडियो बनाने के लिए समय निकालना काफी मुश्किल हो गया था। लेकिन मुझे वीडियो बनाने की बहुत याद आ रही थी, और मैंने बाइनरी टेक लैब्स को थोड़ा अलग दिशा देने का फैसला किया है। तो, क्या बदल रहा है? मुझे GitHub पर कुछ बेहद दिलचस्प फ्री और ओपन-सोर्स सॉफ्टवेयर प्रोजेक्ट्स मिले हैं। इन एप्लीकेशन्स की क्षमताओं को दिखाने वाले कई वीडियो तो हैं, लेकिन इन्हें इंस्टॉल करने और चलाने का तरीका बताने वाले वीडियो बहुत कम हैं। यहीं पर मैं ध्यान देना चाहता हूँ। आगे चलकर, मैं ओपन-सोर्स सॉफ्टवेयर, सेल्फ-होस्टेड एप्लीकेशन्स, लिनक्स, डॉकर और अन्य दिलचस्प प्रोजेक्ट्स पर काम करूँगा। मैं आपको इंस्टॉलेशन प्रक्रिया, कॉन्फ़िगरेशन और समस्या निवारण के बारे में विस्तार से बताऊंगा, खासकर तब जब चीजें योजना के अनुसार न हों। मुश्किल हिस्सों को छोड़ा नहीं जाएगा। ये सिर्फ़ व्यावहारिक ट्यूटोरियल होंगे जो आपको दिखाएंगे कि चीज़ों को कैसे काम में लाया जाए। सबसे पहले है Coolify! हम Coolify को इंस्टॉल और रन करेंगे ताकि भविष्य के वीडियो में हम अन्य ओपन-सोर्स एप्लिकेशन को डिप्लॉय और एक्सपेरिमेंट करने के लिए एक प्लेटफ़ॉर्म बना सकें। 🔗 Coolify: coolify.io 🔗 Coolify GitHub पर: coollabsio/coolify अगर आप मेरी अनुपस्थिति के दौरान भी बने रहे, तो धन्यवाद! मैं वास्तव में इसकी सराहना करता हूँ। और अगर आपको GitHub पर कुछ दिलचस्प मिला है जिसे आप इंस्टॉल होते देखना चाहते हैं, तो मुझे कमेंट्स में बताएं। मैं हमेशा नए प्रोजेक्ट्स की तलाश में रहता हूँ। देखने के लिए धन्यवाद, और चलिए कुछ शुरू करते हैं! #BinaryTechLabs #OpenSource #SelfHosting [id] Saya Kembali! Inilah Perubahan yang Terjadi di Binary Tech Labs Baiklah, sudah cukup lama sejak terakhir kali saya mengunggah video ke Binary Tech Labs, dan saya rasa sudah waktunya untuk menjelaskan ke mana saya pergi. Dan untuk pertama kalinya, saya benar-benar menunjukkan wajah saya di kamera! Pekerjaan saya sebagai administrator kontrak membawa saya ke kamp kerja jarak jauh selama 21 hari berturut-turut, diikuti hanya tujuh hari di rumah. Di antara pekerjaan, keluarga, dan segalanya, menemukan waktu untuk membuat video tentang rumah pintar dan elektronik menjadi cukup sulit. Tapi saya rindu membuat video, dan saya memutuskan untuk membawa Binary Tech Labs ke arah yang sedikit berbeda. Jadi, apa yang berubah? Saya telah menemukan beberapa proyek perangkat lunak sumber terbuka dan gratis yang sangat menarik di GitHub. Ada banyak video yang menunjukkan apa yang dapat dilakukan aplikasi ini, tetapi tidak cukup banyak yang menunjukkan cara menginstalnya dan menjalankannya. Di situlah saya ingin fokus. Ke depannya, saya akan mengeksplorasi perangkat lunak sumber terbuka, aplikasi yang dihosting sendiri, Linux, Docker, dan proyek-proyek menarik lainnya. Saya akan memandu proses instalasi, konfigurasi, dan pemecahan masalah ketika ada hal-hal yang tidak berjalan sesuai rencana. Tidak ada bagian yang sulit yang akan dilewati. Hanya tutorial praktis yang menunjukkan cara agar semuanya berfungsi. Yang pertama adalah Coolify! Kita akan menginstal dan menjalankan Coolify sehingga kita memiliki platform untuk menyebarkan dan bereksperimen dengan aplikasi open-source lainnya di video mendatang. 🔗 Coolify: coolify.io 🔗 Coolify di GitHub: coollabsio/coolify Jika Anda tetap setia selama ketidakhadiran saya, terima kasih! Saya sangat menghargai itu. Dan jika Anda menemukan sesuatu yang menarik di GitHub yang ingin Anda lihat diinstal, beri tahu saya di kolom komentar. Saya selalu mencari proyek baru untuk dicoba. Terima kasih telah menonton, dan mari kita mulai! #BinaryTechLabs #OpenSource #SelfHosting [it] Sono tornato! Ecco cosa cambia a Binary Tech Labs Beh, è passato un po' di tempo dall'ultimo video che ho caricato su Binary Tech Labs, e ho pensato che fosse ora di spiegare dove sono stato. E per la prima volta, mi mostro anche in video! Il mio lavoro come amministratore di contratti mi porta in campi di lavoro remoti per 21 giorni di fila, seguiti da soli sette giorni a casa. Tra lavoro, famiglia e tutto il resto, trovare il tempo per realizzare video su domotica ed elettronica è diventato piuttosto difficile. Ma mi mancava fare video, e ho deciso di dare a Binary Tech Labs una direzione leggermente diversa. Quindi, cosa cambierà? Ho scoperto alcuni progetti software gratuiti e open source davvero interessanti su GitHub. Ci sono molti video che mostrano cosa possono fare queste applicazioni, ma non abbastanza che mostrano come installarle e farle funzionare. È su questo che voglio concentrarmi. D'ora in poi, esplorerò software open source, applicazioni self-hosted, Linux, Docker e altri progetti interessanti. Vi guiderò attraverso il processo di installazione, configurazione e risoluzione dei problemi nel caso in cui qualcosa non vada come previsto. Non salterò le parti più difficili. Solo tutorial pratici che vi mostreranno come far funzionare tutto. Per cominciare, Coolify! Installeremo e avvieremo Coolify in modo da avere una piattaforma su cui implementare e sperimentare altre applicazioni open source nei video futuri. 🔗 Coolify: coolify.io 🔗 Coolify su GitHub: coollabsio/coolify Se siete rimasti con me durante la mia assenza, grazie! Lo apprezzo davvero. E se avete trovato qualcosa di interessante su GitHub che vorreste vedere installato, fatemelo sapere nei commenti. Sono sempre alla ricerca di nuovi progetti da provare. Grazie per aver guardato, e iniziamo! #BinaryTechLabs #OpenSource #SelfHosting [pt-BR] Voltei! Confira o que está mudando na Binary Tech Labs Bem, já faz um tempo desde que publiquei meu último vídeo no Binary Tech Labs, e achei que era hora de explicar por onde andei. E, pela primeira vez, estou mostrando meu rosto na câmera! Meu trabalho como administrador de contratos me leva a acampamentos de trabalho remoto por 21 dias seguidos, seguidos por apenas sete dias em casa. Entre trabalho, família e tudo mais, encontrar tempo para fazer vídeos sobre casas inteligentes e eletrônicos ficou bem difícil. Mas eu estava com saudades de fazer vídeos e decidi dar um rumo um pouco diferente ao Binary Tech Labs. Então, o que está mudando? Tenho encontrado alguns projetos de software livre e de código aberto muito interessantes no GitHub. Há muitos vídeos mostrando o que esses aplicativos podem fazer, mas não o suficiente mostrando como instalá-los e executá-los. É nisso que quero me concentrar. Daqui para frente, explorarei software de código aberto, aplicativos auto-hospedados, Linux, Docker e outros projetos interessantes. Neste vídeo, vou mostrar o processo de instalação, configuração e solução de problemas quando algo não sair como planejado. Sem pular as partes difíceis. Apenas tutoriais práticos mostrando como fazer tudo funcionar. Primeiro, vamos usar o Coolify! Vamos instalar e executar o Coolify para termos uma plataforma para implantar e experimentar outros aplicativos de código aberto em vídeos futuros. 🔗 Coolify: coolify.io 🔗 Coolify no GitHub: coollabsio/coolify Se você continuou acompanhando durante minha ausência, muito obrigado! Agradeço de verdade. E se você encontrou algo interessante no GitHub que gostaria de ver instalado, deixe um comentário. Estou sempre procurando novos projetos para testar. Obrigado por assistir e vamos colocar algo em funcionamento! #BinaryTechLabs #OpenSource #SelfHosting
自己有 VPS 的独立开发者，可以研究下 Coolify。 开源、自部署，支持从 GitHub 部署应用、自动 HTTPS、数据库和 Docker 服务管理。 比每次手写部署脚本省事不少。 注意软件免费，服务器还是自己付钱。 coollabsio/coolify
Coolify: 70,210 titles against 3 fingerprints, and the port that explains the gap Coolify: 70,210 titles against 3 fingerprints, and the port that explains the gap Self-hosted platforms that deploy other software hold deploy keys, environment variables, and database passwords. Coolify is one of them, and its public footprint on 23 October 2026 produced the most unusual set of numbers in this batch. The three measurements ZoomEye returned 70,210 matches for title="Coolify", 3 matches for app="Coolify", and 66,831 matches for title="Coolify" && port="8000". The application fingerprint number is almost useless: three is too small to describe anything, and it suggests the scanner has no stable response signature for the product. The title number is large. The port-constrained number is nearly as large. That last relationship is the finding. Ninety-five percent of the title matches sit on port 8000, which is the port Coolify's own installation documentation assigns to its dashboard. Why that co-occurrence matters When a product name appears in a page title, the match usually includes documentation, blog posts, and project pages. Those live on 443 or 80, served by a normal web host. They do not live on port 8000. A population where the title string and the dashboard port coincide at 95 percent is a population of running consoles rather than a population of articles about the product. That is a defensible inference, and it is the kind of inference a count alone will never give you. It does not follow that 66,831 Coolify servers are exposed and exploitable. It follows that the number is much closer to an installation count than a title count normally is. What a Coolify dashboard controls Coolify deploys applications to servers. To do that it stores credentials for the target servers, the source repositories, the container registry, and the environment of every deployed service. The dashboard is the interface to that store. The architecture decision that matters is how the dashboard talks to the target machines. A Coolify instance that holds SSH keys for a fleet of servers is a single point of compromise for that fleet. A deployment where the same instance is reachable from the internet without a network restriction is a single point of compromise with a public address. Coolify's own documentation covers securing the dashboard, and the interesting question for an operator is not whether the product has a security feature but whether it was configured before the first deploy. Turning the number into a decision The count gives three options. If you do not run Coolify, the number is context: a large installed base with a predictable port means automated scanning against it is worth someone's time. If you run one instance, the check is whether port 8000 is reachable from the internet at all, and whether the account holding the deploy keys is separate from the account you use daily. If you run several, the question becomes whether they share credentials, because shared credentials across instances turn one compromise into a fleet compromise. The port observation also gives a cheap external check that does not require authentication. A host answering on port 8000 with a Coolify title is presenting the dashboard. Whether it then requires a login, a second factor, or nothing at all is visible only in a browser, which is the boundary between what this article can state and what only you can test on your own systems. The measurement lesson, stated carefully Three fingerprints and 70,210 titles is not a contradiction. It is a fingerprinting gap on one side and a string match on the other, joined by a port constraint that happens to be unusually informative. Report the numbers with their queries and the collection date. Say that the port co-occurrence is consistent with running dashboards. Avoid saying that the hosts are unsecured, because nothing in the data supports that, and avoid the opposite claim that the number is meaningless, because the port correlation is evidence. Practical actions Move the dashboard off the default port and behind a proxy that enforces authentication and source restrictions. That single change moves a host out of this dataset and out of most automated scans. Separate the credentials. A Coolify instance should not use a deploy key that also grants access to unrelated infrastructure, and the target servers should accept that key only for the operations Coolify performs. Log the dashboard's authentication events and review them for attempts that succeed after a burst of failures. A public dashboard on a predictable port receives that traffic continuously, and the one success that matters is easy to lose in it. References - Coolify installation documentation, coolify.io - Coolify project repository, coollabsio/coolify - ZoomEye AI query results collected 23 October 2026 for title="Coolify", app="Coolify", and title="Coolify" && port="8000", sub-type all