Veecle Studio: Now Available Directly in the Browser
For years, vehicle software development has been slowed down by local setups, mismatched tool versions, and brittle configurations. Teams spent more time preparing machines and synchronising environments than writing real functionality.
With Veecle Studio, this changes.
Starting today, you can build full vehicle software stacks directly in the browser—with everything centrally configured and ready to go.
(Visual suggestion: DevStudio screenshot in the browser)
Browser-native by default — not by restriction
DevStudio opens instantly into a clean, reproducible workspace. The toolchains, simulators, and MetaModel compiler are already set up. No installation, no dependency drift, no onboarding delays.
This matters because projects are inherently multi-team and multi-target. When each engineer works locally, even a single differing tool version can break a build or test. In the browser, everyone shares the same environment from the first minute.
But this browser-first approach does not lock you into the cloud. It’s simply the fastest way to start.
Cloud when you want it. On-prem when you need it.
Veecle DevStudio is built entirely on containerised workspaces. That means the whole system can run:
- fully in Veecle Cloud
- entirely on-premises (Kubernetes, private CI, restricted networks)
- or in a hybrid setup, mixing both
Air-gapped factories, defence environments, and safety-sensitive domains can host Veecle Studio without moving code outside their own infrastructure. The workflow stays identical.
Prefer local VSCode? Use it.
The browser gives you a complete VSCode experience—but you’re not tied to it. Some teams want the convenience of browser workspaces; others prefer their own editor.
Veecle Studio works seamlessly with:
- local VSCode connected to your DevStudio workspace
- CLI workflows independent of the browser
- normal Git workflows inside your own repo
You choose how you want to work. The environment stays consistent.
A unified environment from design to deployment
DevStudio isn’t just a cloud editor. It’s the central place where architecture, code, simulation, testing, and deployment all meet.
- You model your system architecture: APIs, dataflows.
- You simulate behaviour before hardware exists.
- You mock components with generated stubs.
- You build and validate using automated continuous integration.
- You deploy identical binaries to virtual or physical targets.
Everything is driven by the MetaModel, your versioned description of the entire system.
Everything runs through Veecle OS, the unified runtime across all controllers.
Why this is a milestone
Browser-first development removes the friction that has slowed automotive software for decades. Shared workspaces, reproducible toolchains, on-prem optionality, local-editor compatibility, unified modeling—together they create a development environment that finally moves at modern software speed.
This is the foundation for the rest of launch week.
Tomorrow, we’ll show the advantages of “Instant infrastructure” with Veecle Studio—and why that changes everything.