Create a durmem account, understand its limits, and request help or deletion of your data.
Follow the quickstart, or Install and set up for the full procedure. Use durmem setup to connect supported coding harnesses, or durmem login to add credentials only. Follow the prompts to enter your email, review the Terms and Privacy Policy, and enter the sign-in code. Your first sign-in creates your account. On later sign-ins, durmem asks for consent again if it cannot confirm your current acceptance.
Browser sign-up is also available at <https://durmem.ai/>. Anyone who can receive the email code and accepts the policies can sign up, subject to account availability. Email codes are single-use and expire after 10 minutes; an administrator-issued one-time code can be valid for three days.
If setup is interrupted, retry with the same email and the newest code. If the website reports a store setup problem, use Try again. durmem preserves a completed organization. For capacity or access refusals, see Troubleshooting.
Your email owns one organization: the container for all of your stores. A store is one separate memory; its stores share the organization's encrypted storage volume. This computer reaches each store through a named section in ~/.loom/stores.toml, written by setup or login; you do not need a separate organization setting. See the stores.toml reference for sections and the default store.
Your first sign-in creates the organization with three starter stores, each with its own section:
| Section | Domain | Use |
|---|---|---|
coding | CodingDomain | Your project memory. Setup makes it the default when you have none. |
loom_demo | CodingDomain | A practice store with sample data for the tutorials. |
kanban | LogDomain | An initialized board for optional multi-agent coordination. |
A store's domain decides how its memory is organized and answered; you can change it later. See Manage stores.
Check your signed-in email on the website. whoami reports a harness conversation/agent identity, not your hosted account.
durmem is in a limited public test: the number of accounts is capped, and sign-up pauses when the test is full.
There are two separate limits on your organization: total storage, shared by all of its stores, and the number of stores. The free tier is configured as follows; the operator can change these values, so treat them as the configured policy rather than a guarantee:
| Free-account limit | Configured value |
|---|---|
| Storage per organization | 200 MB, shared by all stores |
| Stores per organization | 5, including the three starter stores |
| Store domains | CodingDomain, PersonalDomain, ReconciliationDomain, LogDomain |
After sign-up, create_store or Manage on the website adds stores; see Manage stores. Creating a store beyond the store limit is refused. When storage is full, saves fail even if you have stores to spare. Delete stores you no longer need, or contact info@durmem.ai about more space.
New hosted free accounts are permanent, with no trial expiry. Older records may contain legacy expiry metadata. If enforcement is enabled, that metadata can lock access. A denied, expired, or locked account may be refused before consent. The operator retains locked data until they delete it or you request erasure. Contact info@durmem.ai about reactivation or erasure.
When the public test is full, sign-up shows The durmem public test is full. Please try again later.; try later or contact info@durmem.ai. This account cap is separate from your organization's storage and store limits. An interrupted earlier sign-up can be retried with the same email.
The durmem operator can read live store data while serving it. At-rest encryption is not end-to-end encryption. Do not save secrets as facts; see Security and privacy for administrator access, backup limitations and network disclosures.
durmem drop_store SECTION --confirm SECTION, or Delete store on the website. This permanently destroys that store's data. See Manage stores before proceeding.Use Log out on the website, especially on shared computers. To forget local credentials, follow Manage stores. Local logout does not revoke copies elsewhere or erase server data. Removing the CLI does not delete your hosted account. See Install and set up.
General, billing and hosted-user support: info@durmem.ai until public issue reporting opens. Report vulnerabilities privately to the same address. Never put vulnerabilities in a public issue.