Sollbase is Protect and Share. Protect runs on the developer machine and checks every command, file, and network call before a coding agent can run it. Share keeps the solutions your team already proved.
PROTECT
The action is checked before it runs.
Commands, files, and network calls wait on your policy.
SHARE
The fix stays with the team.
Search and reuse what already worked.
POLICY CHECK
Piped installer blocked until someone on the team approves it
THE PROBLEM
TODAY
WITH PROTECT
HOW IT WORKS
Protect checks the action before it runs. The model does not get to decide whether a risky action is fine.
One install puts Protect on the machine. That device shows up in your org.
Shell, files, network, and MCP calls are allowed, blocked, or held. Groups and policy sets decide which rules apply.
Held actions wait in Approvals with the exact command. Grants expire. The activity log keeps the record.
WHAT IT CHECKS
Shell, installers, and encoded scripts are matched against the policy for that device.
Reads and writes of secrets, keys, and private config can be blocked or redacted.
Outbound calls and MCP traffic are part of the same decision, not a separate prompt.
APPROVALS
A held command shows up with the exact text, the device, and the rule that caught it. Someone on the team allows it for a limited time, or it never runs. Values that should not leave the machine are redacted before an agent can send them.
DATABASE_URL=postgres://app:[REDACTED]@db.internal:5432/app PAYMENTS_SECRET_KEY=[REDACTED] LOG_LEVEL=info REGION=us-west-2
Protect decides what runs. Share keeps what already worked.