den / Guide / Reference

Run your own den

For teams that need den in their own account: one command deploys it, what it creates, how to update, and how data migrations work.

1 min read · On this page: Deploy · Update · Mail · Backups

Most teams use the hosted den. This page is for the ones that need their own.

#Deploy

npx @pkslabs/den deploy --domain den.example.com

The package ships from pkslabs' own registry; write to support for access before running it.

The command bootstraps and deploys one stack: a function that serves the app, the API, and the MCP endpoint; a table for topics, versions, users, and audit rows; two buckets for artifact bodies and the app; a distribution in front with a certificate for your domain. There are no servers to keep up. The first account to register becomes staff. Sign-up is by invitation after that unless you deploy with --signup open or --signup domains.

#Update

Deploy again from a newer version. A release that changes stored data ships a dated migration; run pnpm migrate against your table after the deploy, with --dry first to preview.

#Mail

Invites and access requests go out through SES from an address on your domain. A configuration set reports bounces and complaints, and den suppresses addresses that bounced permanently.

#Backups

The table has point-in-time recovery and a daily backup; the artifact bucket keeps every version of every object. A logical backup of a workspace is den export --all --all-versions --out <dir>, which imports into any den.