Skip to content

Security by architecture

Your employee works alone. Your data does too.

An autonomous employee needs real access. Molted gives it a private computer and the credentials required for the job—without putting every customer on one shared machine.

The default, not an upgrade

Every Molted starts with its own boundary.

  • One isolated runtime and workspace per employee
  • Credentials encrypted and kept out of public output
  • No shared desktop between unrelated customers
  • Instructions, memory, skills and files remain portable

1 employee

per isolated computer

24/7

managed and monitored

Encrypted

credentials at rest

Portable

workspace and runtime

Four boundaries around the work.

Security is not a badge added after the product. It is how the employee is provisioned, connected and operated.

01

Its own computer

The employee does not borrow a common browser or desktop. Its files, sessions and work stay inside its own isolated runtime.

02

Secrets are not chat messages

Connected credentials are stored as encrypted secrets and injected only where the employee needs them to perform the job.

03

You decide what it can reach

Connect only the accounts and applications required for the role. Remove an account or a capability when the responsibility changes.

04

You can leave with the work

The employee runs on an open runtime. Its instructions, memory, skills and documents remain readable files you can download.

Molted runs the machine. You keep the keys to the role.

We handle the operational surface that normally turns an autonomous agent into a weekend infrastructure project.

Molted operates

Provisioning, runtime health, updates, restarts and the always-on computer.

You authorize

The model subscription, connected accounts, application access and what work the employee is allowed to do.

The workspace remembers

Long-lived files, instructions and memory stay with the employee instead of disappearing after a task.

You can export

The open runtime and plain workspace files keep the employee portable instead of trapping it in a proprietary task history.

Security, without the hand-waving.

Does my employee share a computer with other customers?

No. Every Molted employee gets its own isolated runtime and workspace. It does not work from one shared customer desktop.

Where are credentials stored?

Credentials are handled as encrypted secrets, separate from normal workspace files and conversation output. You connect only the accounts the role requires.

Does Molted train models on my business data?

Molted does not use your workspace or conversations to train models. The data terms of the model provider you choose still apply to that provider.

Can I revoke access?

Yes. You control the connected accounts and capabilities. Disconnecting an account removes that route from the employee's working environment.

Can I take the agent somewhere else?

Yes. The runtime is open and the parts that make the employee yours—its instructions, memory, skills and documents—remain files you can download.

Your Molted could already be working.

Three clicks, fifteen seconds, and the first twenty-four hours are on us.

From $14/mo · live in 3 clicks · first 5 days on us