Seed companies don’t seem to be priced as businesses with intrinsic value derived from future cash flows. Rather than venture capital, they seem to be a proxy for the human capital of the founders and early team.
From our perspective dev container seemed to be what our target audience was already using; as its supported by VS code natively and also as almost all OSS projects are hosted on Github, and their product Codespaces support it as well - it seemed like the logical first standard.
But as mentioned devfile, nix and flox are on the roadmap.
Daytona currently supports only the dev container (https://containers.dev/) "dev env infrastructure as code" standard, but are looking to support others such as devfile, nix and flox.
Thank you! Daytona is an automation tool that soon will support configuration files such as devcontainer or nix, both on the to-do list.
Daytona automates the creation of the development environment on any hardware, whether local or remote. It connects it to a local instance of VS Code (or to a browser if preferred), creates a VPN tunnel to the development environment, and adds a reverse proxy so you can share it as well.
Furthermore, it is acknowledged that an architecture diagram is missing, which would significantly aid in providing a clearer explanation. Efforts will be made to address this as soon as possible.