Live data from Hacker News

Show HN: Alien – Self-hosting with remote management (written in Rust)

news.ycombinator.com

21–30 of 51 posts

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#21
I very seldom, if ever, see a "Show HN" title with a suffix of "written in Java" or "written in python" or "written in Go".

"Written in Rust" seems to be a very popular thing to add.

My assumption is that people know it will get the thread more visibility?

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#22
Is it for managing my software deployed in the customer's cloud environment? Would you support simpler deployment targets, like on premises VMs etc?

At DollarDeploy we developing the platform to deploy apps to VMs with managed services provided, kind of like Vercel for your own servers. Would be interesting to try alien for enterprise customers.

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#23
post #22

Is it for managing my software deployed in the customer's cloud environment? Would you support simpler deployment targets, like on premises VMs etc? At DollarDeploy we developing the platform to deploy apps to VMs with managed services provided, kind of like Vercel for your own servers. Would be interesting to try alien for enterprise customers.

> Would you support simpler deployment targets, like on premises VMs etc?

https://github.com/alienplatform/alien/blob/main/crates/alie... :)

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#24

I like it! I think if we are moving to a world (that is a big if) with more people self-hosting ideas like this one might have a future. A different take: https://www.cloudron.io/

same, I think there are a few folks who are starting to see the feasibility and the desirability in hosting their own solutions. I have been working on an idea to solve this, called minima host[0].

It is intended to be simple: - with the power of a mac mini, you can host (almost) anything - pay for the mini, it is your machine to do with as you please (we will host it for you) - if you decide you no longer need hosting, we will mail you back the machine that rightfully belongs to you

if anyone is interested in becoming a partner, shoot me a message, felipe@ind3x.games

- [0] https://www.minimahost.com/

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#25
post #22

Is it for managing my software deployed in the customer's cloud environment? Would you support simpler deployment targets, like on premises VMs etc? At DollarDeploy we developing the platform to deploy apps to VMs with managed services provided, kind of like Vercel for your own servers. Would be interesting to try alien for enterprise customers.

Yep, I work for small companies and already have a sync server that wish to manage centrally for more than just updates

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#26

> So you're stuck debugging a system you don't control, through screenshots and copy-pasted logs on a Zoom call. This is very real. I work with a deployment that operates in this fashion. Although unfortunately, we can't maintain _any_ connection back to our servers. Pull or push, doesn't matter. The goal right now is to build out tooling to export logs and telemetry data from an environment, such that a customer cou…

> This can be a ton of data though, so we're trying to figure out what to compress and how. We also have the challenge of figuring out how to scrub logs of any potentially sensitive information. This is fundamentally a data modeling problem. Currently computer telemetry data are just little bags of utf-8 bytes, or at best something like list >. IMO this needs to change from the ground up. Logging libraries should emi…

Grand solutions require broad coordination, and they often devolve back into a modified-but-equivalent version of the previous problem. :(

Stream-of-bytes is classically difficult model to escape. Many have tried.

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#27
Interesting approach. The managed self-hosting gap is real..we have run into this exact pain point with kubernetes based deployments where customers modify their cluster configs and things break silently. If I may ask how does Alien handle rollback if an update fails in a customer environment?is there any plan for on-prem/bare metal support beyond the big three clouds?

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#28

Interesting approach. The managed self-hosting gap is real..we have run into this exact pain point with kubernetes based deployments where customers modify their cluster configs and things break silently. If I may ask how does Alien handle rollback if an update fails in a customer environment?is there any plan for on-prem/bare metal support beyond the big three clouds?

Alien is basically a huge state machine where every API call that mutates the environment is a discrete step, and the full state is durably persisted after each one.

If something fails mid-update, it resumes from exactly where it stopped. You can also point a deployment to a previous release and it walks back. This catches and recovers from issues that something like Terraform would just leave in a broken state.

For on-prem: we're working on Kubernetes as a deployment target (e.g. bare metal OpenShift)

Re: Show HN: Alien – Self-hosting with remote management (written in Rust)

#29
post #20

Earlier quoted context omitted.

I agree that keeping things up to date is a good practice, and it would be nice if enterprise CISOs would get on board with that. One challenge we've seen is that other aspects of the business don't want things to be updated automatically, in the same way a fully-managed SaaS would be. This is especially true if the product sits in a revenue generation stream. We deal with "customer XYZ is going to update to version…

This is true even with fully-managed SaaS though. There are always users who don't want the new UI, the changed workflow, the moved button. But the update mechanism isn't really the problem IMO, feature flags and gradual rollouts solve this much better than version pinning

Sure. I'm just saying in the context where fully-managed SaaS was already decided not to be an option, and a customer is deploying vendor code in their environments, the update mechanism can in fact be a problem. It's not just poor CISO management.
Post reply on HN