3 ms·

If anyone on this thread is looking for an alternative, I’m a cofounder of Coherence (withcoherence.com). We offer a netlify-like experience (managed CI, previ

If anyone on this thread is looking for an alternative, I’m a cofounder of Coherence (withcoherence.com). We offer a netlify-like experience (managed CI, preview environments) built on top of your own cloud account. And we also offer an integrated Cloud IDE for use as a development environment. Today we support GCP but AWS is coming soon. To address one comment I’ve seen here with other alternatives, we don’t have the DNS/custom domain limitations of Cloudflare pages. For a static site, migration should be very straightforward and we are happy to help if you run into any issues. Feel free to ping hn@withcoherence.com!

centipixel 4y ago
Static site migration would be very straightforward anywhere. Do you have replacement handling for the `_redirects` file / `netlify.toml`, form handling, `functions` etc All the things that do cause vendor lock in.
- zoomzoom 4y ago
  In general we’re not targeting a 1:1 migration from netlify, so while yes we have equivalents for all of the pieces you mention, they work differently and would require migration work to use Coherence. Coherence offers full-stack containerized application support, so any functions could be run as a backend service - with additional functionality such as databases/redis and wider framework support available (while still getting the benefits we offer such as Cloud IDE and preview environments). As well, we have our own `coherence.yml` file that would replace the `netlify.toml` one. As for redirects, we don’t have anything baked in on that front, but very open to adding equivalent support if it was something our users needed. That’s a good call-out! In the meantime, given our ability to run containers as well as static sites, running an nginx or something with the redirects in the config file would be possible as a stopgap. Thanks for the thoughts!

centipixel 4y ago

Static site migration would be very straightforward anywhere. Do you have replacement handling for the `_redirects` file / `netlify.toml`, form handling, `functions` etc All the things that do cause vendor lock in.

zoomzoom 4y ago
In general we’re not targeting a 1:1 migration from netlify, so while yes we have equivalents for all of the pieces you mention, they work differently and would require migration work to use Coherence. Coherence offers full-stack containerized application support, so any functions could be run as a backend service - with additional functionality such as databases/redis and wider framework support available (while still getting the benefits we offer such as Cloud IDE and preview environments). As well, we have our own `coherence.yml` file that would replace the `netlify.toml` one. As for redirects, we don’t have anything baked in on that front, but very open to adding equivalent support if it was something our users needed. That’s a good call-out! In the meantime, given our ability to run containers as well as static sites, running an nginx or something with the redirects in the config file would be possible as a stopgap. Thanks for the thoughts!