[imiric]

Yeah, the core ideas sound great, but if the only way code can be published and imported is via their cloud platform, that would be a hard pass for me.

Glancing at their docs, I see mentions of Unison Share, which is also hosted on unison-lang.org.

So I would appreciate this being clarified upfront in all their marketing and documentation.

Ah, I do see the BYOC option you mention. It still requires a unison.cloud account and an active subscription, though...

[pchiusano]

Unison code is published on https://share.unison-lang.org/ which is itself open source (it's a Haskell + postgres app), as is the language and its tooling. You can use Unison like any other open source general-purpose language, and many people do that. (We ourselves did this when building Unison Cloud - we wrote Unison code and deployed that within containers running in AWS.)

The cloud product is totally separate and optional.

Maybe we'll have a page or a reference somewhere to make the lines more clear.

[imiric]

I see, thanks. It's reassuring to know that I can use all language features without relying on any of your infrastructure.

[stewoconnor]

yeah, unison cloud is like the "heroku for functions" if you wanna not think about how deployments work. But you can just run unison programs standalone or in a docker container or whatever: https://www.unison-lang.org/docs/usage-topics/docker/

[digdugdirk]

Is a standalone Unison Code instance something that could be deployed in a docker container for personal use?

[stewoconnor]

https://www.unison-lang.org/docs/usage-topics/docker/