Skip to content

Uninstall

Removing ownpaas takes five steps. Steps 3 to 5 delete your labs and cannot be undone.

If you have a licence, open Settings › Licence and choose Deactivate, so the activation can be used on another Mac.

Settings › Engine › Stop. This also removes the LaunchAgent, so the engine does not start again at login. Then quit the app.

Check that nothing is left running:

Terminal window
launchctl print gui/$(id -u)/com.ownpaas.engine # should say: could not find service
pgrep -fl ownpaas

Move the app from Applications to the Bin, then delete the lab and the logs:

Terminal window
rm -rf ~/Library/Application\ Support/ownpaas
rm -rf ~/Library/Logs/ownpaas

This deletes every VM disk, checkpoint and OS image of the lab.

Open Keychain Access, search for com.ownpaas, and delete the items you find. Or in a terminal, repeated until it reports that nothing was found:

Terminal window
security delete-generic-password -s com.ownpaas.context

If you trusted the lab’s certificate authority (for HTTPS in the lab), delete that certificate from the login keychain too.

5. Remove the agent entries and the DNS resolver

Section titled “5. Remove the agent entries and the DNS resolver”
  • Claude Code: claude mcp remove ownpaas --scope user
  • Cursor: delete the ownpaas entry from ~/.cursor/mcp.json
  • Codex: delete the [mcp_servers.ownpaas] table from ~/.codex/config.toml
  • Claude Desktop: delete mcpServers.ownpaas from ~/Library/Application Support/Claude/claude_desktop_config.json

If you used “resolve on this Mac” for a lab DNS zone, delete its file in /etc/resolver/ (needs sudo).

The backups the app made of these files (*.ownpaas-backup-*) can go too.

Uninstalling the app does not touch your cloud account. Gateways, clusters and servers you created there keep running and keep costing money. Delete them in the app before uninstalling, or afterwards in your cloud provider’s console.