10 ms·

Coolify: Open-source and self-hostable Heroku / Netlify / Vercel alternative

• dan_can_code 2y ago
  Very cool options here. I'm always looking for options to throw something on a spare raspberry pi and this looks like a great tool to self-host.
• interestica 2y ago
  [flagged]
  • tabarnacle 2y ago
    I appreciate the caution - and although they're close in spelling, I'd wager coolify is recognized by the majority as adding the suffix 'ify' to 'cool' rather than the term you've highlighted.
    • dkkergoog 2y ago
      [dead]
  • rob 2y ago
    Well then, luckily the name is "Coolify" and not "Coolie."
    • satvikpendem 2y ago
      Wow, a nearly two decade old account, pretty cool, and still recently used too. I find a lot of old accounts simply are not used anymore, for whatever reason. I don't think pg even posts here anymore.
• hk1337 2y ago
  I don't mean it as discouragement but, at least for me, I would choose Heroku or Netlify because I don't want to self host it. I want someone else to manage all those bits for me. It's good experience building the app though and good to have alternatives available.
  • colesantiago 2y ago
    I’m glad that the age of platform decay and VC backed companies that these OSS alternatives exist to counter this destructive trend of extraction based vendor lock in. Vercel, Netlify and Heroku will inevitably not exist in 10-20 years but Coolify will, humming along on a regular VPS.
    • jbaber 2y ago
      As long as you "own" the domain name yourself, so can point anywhere, what's the problem with using a platform and expecting to have to move someday?
      • nine_k 2y ago
        Money, I suppose? Heroku is notoriously trivial to use, and notoriously expensive for the amount of storage and compute you get. A semi-successful but not heavily monetized side project on Heroku could cost you an arm and a leg, while running the same thing on some Hetzner box under Dokku, along with a couple of others, may be not that much noticeable.
    • glenngillen 2y ago
      Heroku has been around for ~17 years at this point. Why do you think it disappears in the next 10?
      • anamexis 2y ago
        Because Salesforce decides it’s not profitable enough to be worth it, or they want to close Heroku off to Salesforce customers, or any number of other reasons
      • matt-p 2y ago
        I mean obviously we're not really privy to market share but I'd say they've had a pretty massive decline in say the past 5 years or so.
      • benatkin 2y ago
• ezekg 2y ago
  Does this project make its money via the cloud offering, or via sponsors? It's kind of unclear.
  • kikki 2y ago
    Both - but primary the cloud offering. The main author (https://x.com/heyandras https://x.com/heyandras) is pretty open about the project revenue its sources. If I remember correctly they're at about 10k MRR mostly from Coolify Cloud. Edit: Latest "post" (xeet?) https://mobile.x.com/heyandras/status/1901894087604916396 https://mobile.x.com/heyandras/status/1901894087604916396 I could find about revenue
• cedel2k1 2y ago
  Love my Coolify Setup!
• maelito 2y ago
  Also checkout Dokploy. Incredible to leave Vercel.
  • s4i 2y ago
    The mandatory link about Dokploy’s unclear/questionable license: https://github.com/Dokploy/dokploy/discussions/3 https://github.com/Dokploy/dokploy/discussions/3
    • sneak 2y ago
      This seems to be an issue in the PaaS space. The guy who runs CapRover illegally changed the license on it to be nonfree, without copyright assignments from any of the contributors who worked on it when it was free software. https://github.com/caprover/caprover/blob/master/LICENSE https://github.com/caprover/caprover/blob/master/LICENSE It’s deceptive, because it starts out saying APACHE LICENSE but then adds a bunch of nonfree provisions to it, making it NOT Apache licensed. It’s especially galling when all of these people are trying to nickel and dime their users with this open core nonsense while their business wouldn’t exist if not for docker, k8s, postgres, mysql, node, php, all being open source.
• 0xbadcafebee 2y ago
  [flagged]
  • slig 2y ago
    I believe that Opalstack is what you're looking for. I've used their service for a while.
  • matt-p 2y ago
    Firstly I think it's a little impolite to frame a opensource project trying to find a sustainable funding model as "weird", whatever your concerns this is still much better than closed source. I don't think the number of people who want to FTP stuff is very high anymore, we are all storing our code in git and therefore want to deploy on a commit or tag. We probably care about SSL, maybe we need to build our code before it can be deployed and so on.
  • Sleepful 2y ago
    This is true for any self-host OSS project. You are pointing at the grass and warning people that it is green.
• pjmlp 2y ago
  Plus points for any language, I dislike how Vercel and Nelify build up on AWS and then we only get JS/TS/Go, or WebAssembly gimmicks.
• huksley 2y ago
  Remember all those horror stories about ridiculous bills from public cloud providers? I also got $4.5k bill once for simple mistake on AWS. So I decided to build Vercel for your own servers - DollarDeploy, which manages servers and deploys NextJS apps (without docker) and docker compose configs to your server. We don't have self hosted or open source but cloud version starts from $1/mo
  • 52-6F-62 2y ago
    Now is a good time to sell licenses around the world. Edit: just noticed you are in Finland. You might be exactly what I’ve been looking for lately
  • frainfreeze 2y ago
    I m curious, how do you deploy Next.js apps w/o docker? Self hosted nodejs? Also how much do you lag behind vercel releases?
    • nine_k 2y ago
      What may be mysterious here? You can have multiple versions of Node installed if needed, and every app brings in the entire dependency tree, isolated from everything else. If you trust your apps enough, you don't even need chroot.
      • CoolCold 2y ago
        I have much more peace of mind when it's not in chroot but even better inside systemd unit and all that ReadonlyPath and capabilities applied. In the ideal case network access beyond localhost and may be db is denied for greater safety
        • nine_k 2y ago
          Sounds quite a bit like a container!
    • huksley 2y ago
• crudbug 2y ago
  I was also looking at alternatives - K8S-based - https://github.com/cozystack/cozystack https://github.com/cozystack/cozystack https://github.com/kubero-dev/kubero https://github.com/kubero-dev/kubero https://github.com/pluralsh/plural https://github.com/pluralsh/plural DCR-based - https://github.com/coollabsio/coolify https://github.com/coollabsio/coolify https://github.com/dokku/dokku/ https://github.com/dokku/dokku/ https://github.com/Dokploy/dokploy https://github.com/Dokploy/dokploy https://github.com/swiftwave-org/swiftwave https://github.com/swiftwave-org/swiftwave Most of these projects are maintained by a single maintainer; for business critical apps look elsewhere.
  • whydid 2y ago
    Because businesses always support their software better than individuals?
    • edoceo 2y ago
      Bus factor maybe? Which is mitigated by good community/contributors
    • cchance 2y ago
      The amount of random 1 man opensource projects holding up industries is shocking XD
      • sublinear 2y ago
        It's worse for corporate private source projects. Often the docs are lacking and it's essentially a 0-man project.
        • dv_dt 2y ago
          0 man + one accounts dept
        • o1o1o1 2y ago
          Second this! I just got hired for a short-term project to extend a payment solution I once wrote when I was employed by that company. I was amazed to find that a) nobody maintained the project after I left, there were only two minor fixes because their house was on fire, and b) I really took the time to write almost complete documentation on all the important topics, which helped me get back on track faster. You are absolutely right, and I have experienced this most of the time. The problem is that it is an uphill battle to explain to most stakeholders why you are "wasting" so much time on non-customer facing documentation. It is hard enough to convince even technical stakeholders (e.g. product owners) to write automated tests. While at the time I mostly think it's bad, later on it forces them to pay me twice as much, so I guess it's not as bad as I always think in those moments :D
• amanzi 2y ago
  I've been using Coolify for about a year now and have been very happy with it. It's really low maintenance, it has built in backups for your apps and databases, decent security by default, and is super easy to use. I log into the underlying VMs once per month to do an apt update/upgrade, and that's about it.
  • ffsm8 2y ago
    Btw, did you know about unattended upgrades? Just curious as the stated reason for the stated reason would become almost unnecessary with that https://wiki.debian.org/UnattendedUpgrades https://wiki.debian.org/UnattendedUpgrades
    • turbocon 2y ago
      I maybe the only person on here that had no idea this is a thing, but thank you this is incredible
    • sgarland 2y ago
      Just don’t do something stupid like changing system Python, because it will silently fail. I learned this the fun way, by inheriting someone else’s travesty of a setup (spoiler: if you have to hardlink random shared libraries to get stuff to work, that’s a good indicator that maybe you shouldn’t have forcibly upgraded the system’s Python installation), and then finding out that despite reporting success, no packages had been updated in the past year. Security lost their minds. I was in awe of the miasma of bad decisions that had been made. Perhaps my favorite was that in the script that created this abomination, it blocked Postgres from being updated automatically via editing a file with sed, but they forgot to use -i, so it just, you know, spat out the modified line to stdout and then went on its merry way. This was not an issue however, since as mentioned, unattended-upgrades was broken, so nothing updated.
    • amanzi 2y ago
      I didn't know about this, thanks!
  • nikodunk 2y ago
• aaomidi 2y ago
  I've been fascinated by how little developers know how to take a service they have, and make it accessible on something like their home network. It's honestly a shocker to me. There's so much knowledge about the stack that gets lost with these services.
  • sgarland 2y ago
    It’s because by and large, web devs do not know computing fundamentals, because they’ve had no reason to learn them. If your language handles memory management for you, why would you learn about it? If poor performance in your app can be dealt with by spinning up more copies of it, why would you spend time profiling your code? And, explicitly to your point, if networking can be hand-waved away by tools like ngrok, why would you need to know how it works? And so on. People who grew up on computers in the 90s, 80s, etc. largely do know these things, because they had to. Understanding those fundamentals, as in any industry, pays dividends. It’s incredibly frustrating to me that at almost all companies I’ve worked for, when I suggest we self-host something instead of forking over millions to AWS, it’s an instant no. The most honest answer I’ve had so far was “that skill set is difficult to hire for.” It is, I agree – and how do you think we got to this point? By perpetuating the status quo, and enriching the hyperscalers, who seem to have no problem hiring for that skill set.
    • aaomidi 2y ago
      > when I suggest we self-host something instead of forking over millions to AWS, it’s an instant no. This is something that bothers me a lot, and I've given up. It's to a point where we're paying thousands of dollars sometimes a year for 200 lines of code. It also kinda makes it harder to sometimes just practice engineering skills. For example, I wrote a just in time access request solution at work. However, okta also has one of these. Funny thing is, the one I wrote is a proof of concept - so it's a little rough around the edges but nothing spectacularly wrong. I then used the okta solution for this and my god, what an absolute mess of software they have. 1. They don't have the ability to have the requester specify a duration of access they want. It all has to be hardcoded. 2. Imagine you request access to group A for 3 hours. 2.5 hours later, you're thinking "Hmm, I think I'm going to need more access. So you make another access request for 3 hours. After half an hour that first access expires, and just removes your access. Even if you still have 2.5 hours left from your second access. 3. Without even trying, I got the backend for setting up the access requests into an inconsistent state. Okta's UI is insisting I can't delete a group because it's used by an access request form. However, when I was making that access request form the save button partially failed, so now there's this dangling foreign key somewhere in their database. Inconsistencies like that in software that's supposed to be the source of truth of access is just absolutely unacceptable. 4. Okta "removes" access by removing you from the group that you had requested. However, if there's any issues with Okta's provisioning code, from Okta's perspective you don't have access but the third party service might still think you do. They don't _remove_ the access from the third party first before removing it from their own source of truth. What's depressing is that in my proof of concept, before even trying Okta's product I thought about and planned around all of these problems. --- Anyway rant over, but at least in hiring I am very adamant about the candidate knowing how to get a basic website up and running and understanding NAT/Port Forwarding/HTTP(S) Proxies. Why? Well, when our customers run into issues with our software our engineers need to have the fundamentals to help troubleshoot.
• icelancer 2y ago
  Had a bunch of problems trying to host / run this on an internal-only network.
  • peaklabs-dev 2y ago
    Exactly what problems did you have?
• pier25 2y ago
  Tried it for a bit. Paid one month of the subscription. The dashboard is incredibly clunky and at the time they didn't have SSL for db connections (not sure about now). A lot of stuff you need to know what you're doing like configuring tags for Traefik etc. The deal breaker was it didn't have zero downtime deploys. Any pending request when you update an app is simply killed. I was expecting something like Heroku or Vercel but this ain't it. Ended up concluding that if I wanted to run/deploy apps on my own VPS I'd just use Kamal or Dokku. Both have zero downtime deploys, certbot, proxy, etc.
  • msy 2y ago
    Kamal has a lot of rough edges (still can’t support custom certs for example) but is still a far more mature solution. It does less but better.
    • IgorPartola 2y ago
      Kamal proxy is good enough to sit behind a load balancer. I would not let it be what a client sees. There are some major features missing and it just hasn’t been battle tested enough to be subjected to DDoS type traffic, etc. Overall, I do like the Kamal approach which basically boils down to the fact that instead of a complicated cluster orchestration system the developers decide which machines code runs on. Once it has real support for doing DB migrations as a part of its deploys, a proxy that is less magical and more feature rich, and its CLI fixes some poorly documented and frankly somewhat annoying issues it will be a real workhorse. I am also curious about Dokku + k3s. I have used Dokku for a long time but only on a single host.
    • psviderski 2y ago
      What’s your use case for custom certs? Why are the automatically issued Let’s Encrypt ones not enough?
  • shash7 2y ago
    Had the exact same experience. Incredibly clunky UI/UX. For docker-compose, I had to create a specific one for Coolify because it goes and does its own magic. Tried Dokploy(similar service), better UI but lacking in docs. In the right hands, these products could be so much better.
• W6zVktFA 2y ago
  Coolify unfortunately didn't click with me, and I had a bad experience with a Redis database, so I stopped using it. I would recommend Elestio (eles[dot]io) as an alternative which isn't open source, or self-hostable, but met my primary goal of drastically reducing cloud costs. And you can bring your own cloud/server, though I'm choosing to also rent from Hetzner through Elestio. I'm running two redis databases on machines with 3 cpus, 4gb ram, and 80gb storage for about $80 total (the machines are billed hourly, but you get the max monthly bill up front).
  • hnroo99 2y ago
    Interesting, what was bad about your Redis experience on Coolify? I was just about to do the same for a personal project.
  • SomeUserName432 2y ago
    > Coolify unfortunately didn't click with me, and I had a bad experience with a Redis database, so I stopped using it. I tried using coolify and I gave up due to every ~third redis connection failing to connect. No idea what was up with that, ended up going with CapRover.
  • peaklabs-dev 2y ago
    What was the issue you had with Redis?
• steve_adams_86 2y ago
  I’m happy using coolify. I self host on my Mac Studio as the control plane and deploy to digital ocean. I’m currently looking to host in Canada instead, but not having much luck. I considered hosting my deployments locally as well, I don’t get much traffic, but haven’t made a decision yet. Overall it’s good software that just does what it says it will. My needs aren’t particularly complex, but they aren’t totally trivial either. It does a great job orchestrating things without me needing to worry much about the inner workings. I’ve done these things manually for a long time and I would be fine continuing to do that, but… I’ve got a job, kids, other hobbies, etc. It has been great to have a simple control plane to automate a lot of it for me. I find it makes it more likely for me to build and deploy something in the first place, which is what really counts for me at the end of the day. The discord has also been a good resource. They’re very helpful and the vibe is very positive in my experience. It has been, and still seems like an ecosystem worth investing in.
• satvikpendem 2y ago
  Coolify is cool, pun intended, but a bit clunky (maybe due to the PHP nature of it), I recommend Dokploy these days.
  • peaklabs-dev 2y ago
    A new UI is being planned and developed as we speak, so the UI/UX will improve a lot. PHP has nothing to do with this.
    • satvikpendem 2y ago
      By PHP I meant more that it causes full page renders (ie server side rendered) vs client side rendered frameworks like React.
      • peaklabs-dev 2y ago
        I understand. We recently made a change that makes all pages render like a SPA, so no full page reloads anymore, that said we are developing a new UI, most likely with vue.js.
• LeicaLatte 2y ago
  I would love to move away from railway to Coolify or dokploy. Someday.
• matus_congrady 2y ago
  I'm sorry for being a bit off-topic, but I'm a founder of a PaaS company myself, and I think that what we offer is a great alternative to Coolify for companies that need a more "managed" and reliable infra. https://stacktape.com https://stacktape.com is a Heroku/Vercel-like PaaS platform that deploys directly to your own AWS account. It supports both serverless (lambda functions), and serverful (AWS ECS Fargate or EC2) deployments. Besides that, it supports other AWS infrastructure resources, such as RDS MySQL/Postgres, Redis, ElasticSearch, etc.. You can deploy from console, using git-push-to-deploy, or even use preview deployments (ephemeral environments for every PR). Compared to alternatives, it's both very easy to use, and flexible/extensible at the same time. You can use it to quickly deploy anything in a few minutes, yet it will be sufficient to cover even complex infrastructure needs you might run into in the future.
  • elorm 2y ago
    It’s very much on-topic. You’re just shilling your own product under the thread of a similar product, nothing to be ashamed off chief. Shill away.
    • matus_congrady 2y ago
      It's completely true, and I AM ashamed for doing it. But it's a terrible time to be a PaaS founder, since there are very few new projects being started at the moment. Without exaggeration, I think there are somewhere between 10% and 20% of new projects being started (which is the only point people will actually choose to use our platform) compared to 2022. Hard times, lower standards. Sorry. We've got ~40 website visitors from that comment so far, and I can't pass on that.
      • vinibrito 2y ago
        Well, what did you see that gave you that impression? About less new projects being started. This got me super curious.
        • matus_congrady 2y ago
• ofrzeta 2y ago
  No idea why there's almost no PaaS solution for Kubernetes. It would be a great platform with some add-ons. I know there's Porter but only on AWS and Azure if I understand correctly. Which is fine for many use cases I guess. Still I want to self-host for dev without huge cost. There's also Korifi which implements the Cloud Foundry API on Kubernetes but it's still in progress and its future might be uncertain.
  • SalariedSlave 2y ago
    What about https://syself.com/ https://syself.com/ ? Haven't used it yet, but I read about in on HN and bookmarked it for future reference..
    • ofrzeta 2y ago
      I hadn't heard about it but it seems just like management for Kubernetes not a layer on top to enable PaaS, although it has managed databases. Also it doesn't seem to be open source. Thanks for the pointer, though.
  • sgarland 2y ago
    Did you see [0] above, from crudbug? They listed a few. [0]: https://news.ycombinator.com/item?id=43588786 https://news.ycombinator.com/item?id=43588786
  • peaklabs-dev 2y ago
    We are currently investigating and planning something for scaling, so stay tuned, it may happen soon.
  • pjmlp 2y ago
    Azure Container Apps?
• NitpickLawyer 2y ago
  Perhaps a bit tangential on the subject, but in the same spirit - does anyone know of an open source self-hostable alternative to runpod/vast for managing your GPUs? Our small team has some bare metal servers and I'd like to try something light to manage / reserve instances w/ the convenience of a webui and a place where the team can see at a glance who is using what, and eventually some notes on how long each deployment is likely to take (self filled ofc).
  • breadislove 2y ago
    we are using claudie(.io) together with ray. but we put a lot time into the infrastructure but we managed to cut our cost for a factor of 20x by doing this.
• theanonymousone 2y ago
  I have also been using Coolify happily since its early(?) days (mid 2022 IIRC). One big plus for me is that there is nothing to be installed on the client: No CLI, etc. In my specific use case, I switch laptops I work with, so it's a huge advantage that I can just open the UI in the browser and do my work. Of course there is room for improvements in many corners of it, but I couldn't get any of the alternatives to works the same way, yet.
  • TechDebtDevin 2y ago
    One alternative that works is an nginx reverese proxy and 10 minutes of configuration :P
    • deleted 2y ago
      [deleted]
    • theanonymousone 2y ago
      Replacement: I wrote something here and then deleted it. You may also want to rethink about your comment.
    • peaklabs-dev 2y ago
      Then you have not tried Coolify and all its features.
• intev 2y ago
  Anyone know how this compares to caprover?
  • peaklabs-dev 2y ago
    Coolify is much more feature rich and well maintained with a clear open source license.
• ksajadi 2y ago
  I have a big issue with any self hosted alternative to name your paas here. Every time I try one I find myself maintaining the PaaS instead of maintaining my app, which defeats the whole purpose of a PaaS
  • peaklabs-dev 2y ago
    I know that feeling, we are constantly improving the stability of Coolify, so we hope that this is not the case with us.
• upmostly 2y ago
  Tried this but ended up building our own competitor: Hypership.dev We're solving slightly more than what Coolify are by providing Auth, analytics, event tracking, an admin dashboard and more.
• zachlatta 2y ago
  I highly recommend Coolify. I evaluated every option when looking for a Heroku alternative, and Coolify is clearly the best as long as you don’t absolutely require zero downtime deploys. We are hosting over 100 services on it for https://hackclub.com https://hackclub.com and it’s been great. We’re 3 months in now. The key is to think about it as a GUI on top of Docker, not as a fully managed solution. It’s one of those PHP apps that’s weirdly reliable. I see lots of other comments recommending Dokku / Dokploy / others. None of those options are nearly as mature as Coolify in my experience.
  • huesatbri 2y ago
    I’ve been using Dokku for 7 years and counting, both professionally and for hobby stuff. It’s a very mature project that has never gotten in the way, and keeps getting better.
  • rodolphoarruda 2y ago
    FYI your clubs directory is down. (at least for me)
    • zachlatta 2y ago
      Thank you so much! Will investigate.
  • samfundev 2y ago
    Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/64098f4bbc4ee906a66896757d30589c286db702/docs/knowledge-base/rolling-updates.md https://github.com/coollabsio/documentation-coolify/blob/640...
    • cromka 2y ago
      It seems to be killing all remaining connections, as it just stops old container when new is deemed healthy. So not completely downtime by definition, is it?
• scottydelta 2y ago
  I highly recommend coolify. Been hosting it on a dedicated server with 16 core and 64 GB ram and it powers following things for me right now - prefect for ai and other automations. - metabase - postiz - open webui - jupyter notebook - few experimental Db backup is an issue but the best way I have found is to create a dedicated folder for your containers volume and edit docker compose in coolify UI to use this path for all volumes. Now you can backup coolify data and this container volumes folder. You can assign a wildcard subdomain to it and it can then assign subdomains easily to any project with ssl. Pretty nifty. Think of coolify as ui for docker and other network things on server. I use lazydocker to manage containers via command line too on server when coolify won't bend to my will. So both combined together gives a solid control and ease.
  • peaklabs-dev 2y ago
    Backup improvements are planned and under investigation. The only major issues with backups for non DB containers is that they need to be stopped to ensure data integrity. We are investigating some filesystem level snapshots, but not sure yet.
• amclennon 2y ago
  I have been super happy using Coolify to self host automatic preview branches from pull requests. I'm not sure if it's necessarily mature enough for me to trust it with production loads, but it's extremely easy to get started with the Github integration and wildcard subdomains
  • peaklabs-dev 2y ago
    Thanks for using it, there will be many more features to make it even more production ready and stable in the future.
• mrcwinn 2y ago
  I argue a "self hosted" alternative to "Heroku / Netlify / Vercel" is by definition not an alternative to "Heroku / Netlify / Vercel".
  • pyb 2y ago
    Not having to self-host is 80% of the point of these services
  • franga2000 2y ago
    The main selling point of these is deployment, management and application-first approach. Whether you have to first rent a VPS and curl|bash an installation command is not an important detail for many use-cases.
• andrasbacsai 2y ago
  Hey, the dev behind Coolify here. We are working on a new UI, and to be even more mature, and a lot of other things, because now I am not doing this alone as I used to for years.
  • peaklabs-dev 2y ago
    Yes, lots of exciting stuff coming soon.
  • galuggus 2y ago
    Thanks. I find coolify very useful.
• diamondfist25 2y ago
  Anyone use easypanel? I’ve been using them and it’s been the easiest. They have a bunch of templates for open source projects, so u can click and deploy them easily
• morteify 2y ago
  I really wanted Coolify to work, as I like the idea behind it. I gave it a go some time ago, and I ended up spending the entire evening battling issues like the proxy not running, with no helpful UI feedback whatsoever. So I came to the conclusion that if I have to dig through abstractions built by someone else, only to find out that in the end I have to manually restart the underlying containers anyway, I might as well stick to using Docker directly. And truth be told, it’s not even that difficult to handle it all yourself. And it’s definitely very educational. It gives me a nice feeling of being in control and knowing my server. And on top of that it’s fun too.
  • peaklabs-dev 2y ago
    Many stability improvements and a new UI/UX are coming soon.
• catlover76 2y ago
  If I'm in the market for Heroku, why would I want to self-host anything?
• rc_kas 2y ago
  This project is amazing! I been messing with it all day today, I'm in love. Thank you to the developers, you really have a keen eye for detail.
  • peaklabs-dev 2y ago
    I am glad you like it. If you have any problems or questions, just let me know.
  • bberenberg 2y ago
    I think it’s pretty good, and it’s good to hear they’re working on better deploys and UX. But the big thing to note is backups. There just isn’t a good way to use this with critical data without bolting on some kind of custom backup solution. I am always terrified the hetzner server with all my random stuff will die before I get around to implementing a solution.
    • peaklabs-dev 2y ago
      We are also working on backups. The only big problem with backups for non DB Containers is that they need to be stopped to ensure data consistency, so we are looking at some filesystem level options but not sure yet.
      • bberenberg 2y ago
        Good luck! For what it’s worth I hope you prioritize this above everything else.
• dboreham 2y ago
  Having built similar things in the past, raising a bit of an eyebrow at the business model: it seems likely that with three parties involved (Coolify people, customer, hosting provider) there will end up being too much finger pointing as to the source of issues. Certainly way too much to cover a few dollars a month revenue. I think most customers would conclude they are better off just deploying the bare OSS version and paying whoever they are already paying (internal or external) for engineering services, to make sure it stays up.
• 999900000999 2y ago
  What's the actual point of the paid product if I still have to host my own stuff? Does it just manage things? Is it actually open source with usable instructions, or is it magic like Superbase that requires digging through GitHub issues to find the secret truck to getting things to work. How does it compare to Captain Rover ( which was awesome until it just stopped working one day, luckily my backup script captured my blog before this happened). At this point I'll just give Render 7$ a month. When it's 3am I don't want to figure this out by myself. In a Corp environment I'll let the dev ops team sort it out.
  • peaklabs-dev 2y ago
    Coolify Cloud lets you connect your own servers in pretty much 1 click and then just deploy resources, you do not need to worry about upgrading Coolify, instance backups and so on, we manage all that for you. Yes, Coolify is completely open source and all features are completely free - the cloud and self-hosted versions are completely the same and the hosting is pretty simple.
• jurajmasar 2y ago
  We did a video on Coolify vs Dokploy https://www.youtube.com/watch?v=1POdazLoiRE https://www.youtube.com/watch?v=1POdazLoiRE
• oldgregg 2y ago
  Been running Cool for about a year. Drop a couple thousand on a 1U and throw it on a $100/mo colo and it's crazy bang for the buck. It makes it so easy to spin up new projects it's hard not to like it. Definitely when launching some containers and open source projects it's not as seamless as it could be-- can require fiddling with vars and compose files-- but on the whole very stable, lightweight, fast deploys, and conceptually pretty simple. One thing I've noticed is I've starting using much more open source software for various things. When you can just jump into the UI, paste in the github link, and have it running on a wildcard domain in 60 seconds I find myself giving OSS a try more often before looking elsewhere.
• timsh 2y ago
  Been using coolify to host my blog + analytics + a couple personal projects for around 6 months. Good for 1-click installs that “don’t need” a lot of maintenance, like Ghost, Plausible, etc. Had some issues with spikes in CPU usage (similar case: https://github.com/coollabsio/coolify/issues/3226 https://github.com/coollabsio/coolify/issues/3226) Monitoring is not enough but I just go straight to the container im looking for and htop it. For not 1-click I still sometimes feel like bumping into a brick wall, and go for a standalone docker-compose setup outside of coolify. Coolify is too high-level to debug small Docker intricacies (or maybe it’s that I’m bad with that).
• ecralx 2y ago
  Started using Coolify (self hosted) for ~6months now and I love it ! Works great with most of the stuff I deploy (react SPAs, python/fastapi stuff, hugo). Sure, I can do my proper setup, but tbh I just want to go fast sometimes and Coolify is great for that. For DBs and cache, didn't test it though, but willing to next time I have a personal project ! Great stuff, thanks for your efforts and keep up the good work !