Deft is a self-hostable workspace where people and agents share conversations, tasks and company knowledge. You can use the workspace without an AI provider. When you connect one, agents work through scoped tools and review policies.
The project is in alpha. Use a named preview for evaluation, read its release notes before upgrading, and keep a tested backup of your workspace.
The general workspace baseline in the table below is v0.3.0-preview.15, a core release. The connected-App developer-preview set is v0.3.0-preview.120/schema120 with independent Email App13/Runtime15 and public Kit38/Kit35. Use the compatibility manifest for exact public artifacts and App release boundaries for current scope. Its explicitly Apps-enabled profile differs from the general default-off configuration.
Development on master may include changes absent from the published image.
| Capability | Availability | How to start |
|---|---|---|
| Chat, tasks, notes, Knowledge, calendar and team administration | Available in the published preview | Install Deft |
| Defty | Available when an operator configures a supported AI provider | AI and agent limits |
| Personal MCP access | Available; authentication and client support vary | Connect an AI client |
| Standalone Modules | Available; install a manifest in Settings → Modules | Build your first Module |
| Internal App packages | Experimental and disabled by default; package declarative resources with App Kit | Build an internal App |
| Connected Apps and bounded scheduled actions | Included in the published preview; experimental and disabled by default | Connected App author guide |
| Certified Hermes bundle | Release-specific historical support; excluded from preview.15 | Read the chosen release's compatibility and certification notes |
| External Runtime, governed source sync and trusted App UI | Available in the scoped Apps developer preview; requires reviewed setup and compatible artifacts | Connected App author guide |
| Arbitrary custom App UI and public portals | Planned; outside the trusted renderer contract | Roadmap |
| Hosted Deft service | Not currently offered | Self-host using the supported Docker Compose path |
Standalone Modules do not need the experimental Apps flags. See Modules and Apps for the two installation paths.
Apps require DEFT_APPS_ENABLED=true on the API and
NEXT_PUBLIC_FEATURE_APPS=true in the web build. Connected execution needs
DEFT_APP_RUNS_ENABLED=true, DEFT_APP_RUN_APP_ORIGIN_ENABLED=true and a valid
DEFT_APP_RUN_KEYRINGS secret. Bounded automations also need
DEFT_APP_AUTOMATIONS_ENABLED=true. Follow the operator guide
when enabling these together. Flags do not grant an App permission: its package
and requested access still need operator review.
The example configuration leaves these features off. See the author and operator
guides before enabling them; do not assume an image was built with an opt-in UI.
Deft is authoritative for the shared workplace record and access to it. Its supported tools enforce workspace permissions; governed actions follow approval policies and produce attributable receipts. Ordinary workspace edits retain the history provided by that feature. Personal MCP access acts with the permissions of the person who authorized it.
An external agent can also have private memory, its own skills, model settings and tools. Its operator owns those choices and the costs they incur outside Deft. Deft-side limits are not a cap on every action or model call that runtime makes. Shared Knowledge and private runtime memory serve different purposes; connecting an agent does not give Deft control over the agent's entire execution environment.
A Module describes domain records, relationships and native views. An App packages supported extensions for review and installation in a workspace. Connected Apps can request additional supported capabilities, subject to a separate review.
Start with an internal workflow, such as tracking vendors and linking their records to tasks. A public vendor portal also needs external-user access and custom experiences that the current general App contract does not provide.
Follow Getting started to create a small workspace, connect a personal AI client, or build a supported internal App. Each route identifies the prerequisites and the result you should see. For operating limits, read Current limitations; for changes between versions, read the Changelog.