- Is a coding agent subscription included?
- No. Your engineers sign in to their agents with their own vendor subscriptions, and the vendors bill them directly. We show calculated cost for orientation only.
- Is there a vendor lock-in?
- No. The agents are the unmodified vendor CLIs and the code lives in your Git repositories. Run the agent on a laptop again, check out the repository, and you are where you were.
- Can I pause a workspace?
- Yes. A paused workspace releases its compute and keeps its disk at a small paused rate, so a client project can rest for weeks. Resume it and continue where you stopped.
- Can I run this on my own cloud?
- Yes. The hosts, or the whole system, can run on your own infrastructure. Contact Fabian Wesner for details (fabian.wesner@tecsteps.com).
- Can I cancel?
- Monthly, with no minimum term. Workspace hours are prorated to the hour, so you pay for what ran.
- How much memory and CPU does a workspace really get?
- The pricing page lists ceilings, because workspaces are burstable by default: half the memory figure is guaranteed at all times, and the rest plus the CPU are there whenever the host has room, shared fairly with neighbours. That fits most work. If a workspace needs its full memory and CPU at all times, you can reserve them for a surcharge in the app.
- Can I still use laptops?
- Of course. Engineers use daemons.run from their laptops, from the IDE, the CLI, a browser or the phone. They can also keep running coding agents directly on the laptop, but we do not recommend it: work on a laptop is neither governed nor secured, and it stops when the lid closes.
- Is my code and data protected?
- Yes. Every workspace is its own virtual machine with its own disk and network, and its engineer locks it with a PIN that is verified inside the workspace and never stored on the platform. Terminal, files, editor, SSH and previews stay refused until that PIN is entered, so whoever breaks into the platform still cannot open a single workspace. Nothing is pulled out of a workspace: only counts and health leave it, and nobody at daemons.run can look at your code or data.