Platform Enablement

• BYOC for POCs: We've enabled Bring Your Own Cloud (BYOC) support for Proof of Concepts (POCs), allowing greater flexibility for trial users to integrate their preferred cloud environments.
• Storage Mounts in Production: Storage mounts are now live in production and ready to use, enhancing data accessibility and management across the platform.

Product Enablement

• GitHub Action Runners: We've introduced GitHub Action runners that support actions using Docker, streamlining your CI/CD workflows.
• Native Windows CLI Support: Our CLI now natively supports Windows, improving the experience for developers working outside of Linux environments.
• Build Log Enhancements: We've refined the formatting and usability of build logs, making it easier to track and troubleshoot builds.
• Headless Client Enhancements: Personal Access Tokens (PATs) are now exposed to the end-user in both the CLI and UI, providing more transparency and control.
• General Improvements: Various bug fixes, UX enhancements, and performance optimizations have been implemented to improve overall product reliability and user experience.

Developer Enablement

• Notification Drawer: We've added a notification drawer to keep you informed when a job (e.g., recipe build, workspace launch) is complete, allowing you to navigate the site without waiting for processes to finish.
• Recipe Writing Enhancements: A documentation window has been added to the recipe editor, making it easier for users to access information about recipe syntax directly from the editor.
• Recipe Editor Improvements: The recipe editor has undergone several ergonomic and aesthetic improvements to provide a cleaner and more user-friendly experience.
• Onboarding Enhancements: We've completed the onboarding steps related to publishing a recipe, making the process clearer and more intuitive for new users.
• Public Repo Support for Suggestor: The suggestor can now run on public repositories, offering suggestor steps for users working with public codebases.

After coming out of a pretty long build cycle, we have narrowed in on a few core primitives that we will expose:

• Compute (isolated VM/container orchestrated using a base Kubernetes cluster)
• Network (based on Wireguard; using Tailscale's open source)
• Storage (based on Ceph)

We call a combination of these, a Workspace. A user configures a workspace by writing a Recipe. To improve the iteration speed for building a recipe, we chose to host a builder (based on buildkit in our control plane) so we can optimize builds speed by caching layers. The main development environment in the workspace, that you can connect your local IDE/terminal to is based on sysbox-runc, along with a few other modifications to how those workloads are run - this is to make the environment look and feel like a VM (eg: running docker normally rather than using various workarounds and/or introducing security issues).

Each workspace also comes with its own virtual Kubernetes cluster (loosely based on vCluster).

Next updates will cover more in-depth details on each of these areas. Onwards!