Documentation | Dweve Developer Docs

Sales, engineering, DPO, or press. All addresses are monitored.

Books, certification tracks, and courses when you want depth.

Technical writing explaining the constraint-reasoning architecture.

Foundation libraries you can run, inspect, and contribute to.

Privacy, pricing, product, and deployment answers in plain language.

If a doc set is missing, a page is wrong, or an example does not run, that is a bug. File an issue on the relevant GitHub repo, or write to support@dweve.com. Every gap is a candidate for the next sprint.

, with a public source link or access route for each project

Open-source documentation sets are published at

Every foundation project gets its documentation at docs.dweve.com when its repository is published, in the fortnightly rounds that start on 1 September 2026. Each entry in the side panel shows where that project sits in the order.

. Each product page on this site links to its doc set in the side panel.

Product documentation sets are published at

Each product ships its own documentation set: architecture, getting started, API references, deployment recipes, and changelogs. The product doc sets come online at docs.dweve.com from September 2026, alongside the first invite-only round.

Per-product and per-project documentation, generated from each repository. Architecture references, getting-started guides, tutorials, how-to recipes, API references, and changelogs. Open the doc set for what you are working with.

Jacquard, Forge, HEDL, and Mycelia are research workstreams, not commercial product documentation and not ordinary open-source library entries. Their documentation focuses on methods, experiments, datasets, constraints, and publication notes.

Research documentation sets are published at

. Each research page on this site links back to the corresponding notes when a set is available.

The first steps: signing in, asking your first question, and finding your way around.

Simple how-to guides for the things you will do most, written for beginners.

Quick answers to the questions people ask us most often.

How your information is kept safe, and why nothing happens without your say so.

You do not need to read everything. Choose the topic that matches what you want to do and we will open that part of the docs for you. Each one is written in plain words, with pictures and short steps, so you can follow along even if this is all new to you.

Links open docs.dweve.com in a new tab, so you never lose your place here. The site goes live in September 2026.

Everything lands at docs.dweve.com from September 2026.

Our documentation is made to be read by anyone. There is no manual to buy and nothing to install to read it. Open the site, pick your topic, and follow the steps. If something is still unclear, there is always a real person you can ask.

Short steps you can do at your own pace.

No jargon and no assumptions. If a word needs explaining, it is explained.

The docs live online, so they are always the latest version. Nothing to download.

If the docs do not answer it, you can always reach a person who will.

From September 2026, everything you need to get going is on docs.dweve.com, written in plain language and free to read. Until then, we are one message away.

A guided path from first sign-in to a working setup for your team.

How each product works and how to use it, one guide per product.

Managed Fabric, licensed customer operation, edge or air-gapped, with the trade-offs spelled out.

GDPR workflows, audit trails, data residency and the EU posture.

Rolling the platform out to the people who will use it every day.

How to reach us, what is covered, and where to send a question.

Managed Fabric on the public Dweve Mesh. No direct product operation required.

Run it on your own infrastructure, fully under your control, from install to daily operation.

A low-ops edge profile for teams that already live on the edge, close to where requests arrive.

A conventional container profile for your platform engineering, with the manifests you expect.

Local-only operation with Dweve, no external model calls and nothing leaving the network.

Audit trails, retention, consent and data-subject workflows, ready for a reviewer.

Each product has its own documentation set on docs.dweve.com: what it does, how to configure it, and how it fits with the rest. Because it is one platform rather than a dozen bought-in tools, the docs read as one coherent library instead of a stack of vendor manuals that contradict each other.

Start with the product you are evaluating, or read across them to see how the whole platform holds together.

Sovereignty and compliance are practical questions, so the docs treat them that way. The deployment guides distinguish managed Fabric on Dweve's public Mesh from customer-operated licensed estates, including fully air-gapped operation. The governance guides cover GDPR workflows, audit trails, data residency, and the commercial boundary between service access and direct product operation. You can hand these to a security reviewer and they will find real answers, not marketing.

Managed Fabric, licensed operation, edge, Kubernetes and air-gapped, side by side.

Where data lives and how the tenant boundary is drawn.

Subject requests, export and erasure as documented processes.

What is recorded, for how long, and how to prove it.

Product guides, deployment profiles and compliance references all live on docs.dweve.com. Point your evaluators at it, or talk to us about your rollout.

The full HTTP API surface, endpoints, schemas and auth, generated from the source.

Typed clients and CLIs, with install, auth and end-to-end examples.

How the stack fits together, from Core up through Loom, Nexus and the rest.

Run the platform yourself: infrastructure, configuration and operations.

The workflow engine, triggers, webhooks and the evented layer underneath.

Every setting, environment variable and adapter, documented and typed.

Get any of the fourteen projects running in a few minutes.

Generated reference docs for every crate and package.

Runnable examples that show each library in a real context.

Build from source, run the tests, and open a pull request.

Binary constraint discovery and the ideas the platform is built on.

The research written up in the open, with methods and results.

How the numbers are measured and how to reproduce them.

Each commercial product has a full documentation set on docs.dweve.com: API reference, SDK and client libraries, architecture notes, configuration and self-hosting. The reference is generated from the source and versioned alongside it, so what you read matches what runs. Start with the product you are integrating, or read the architecture to see how Core, Loom, Nexus, Spindle, Mesh, Aura, Fabric and Charter compose.

Kera, the fusion-graph substrate, has its own reference in the same site.

The getting-started path on docs.dweve.com takes you from an empty project to a working integration: install the SDK, authenticate with an API key or OAuth, make a first call, wire it into a workflow, and deploy. Every step is copy-paste runnable and the same across the typed clients.

A mock provider for deterministic tests.

The fourteen foundation projects have project-specific access terms. Each carries documentation on docs.dweve.com from the round in which its repository publishes, and its page names that round.

Each entry links to the docs and the available source path.

The research programmes are documented in the open on docs.dweve.com: the binary constraint discovery approach the platform is built on, the papers and write-ups with their methods and results, and the benchmarks with instructions to reproduce them. Forge, the program-synthesis programme, and Mycelia, the artificial-life work, are covered here as active research.

API and SDK reference, self-hosting, architecture and the open-source quickstarts all live on the docs site, versioned with the code. Follow the source link or contact engineering when access is by request.

Each product keeps its own documentation set on docs.dweve.com, and every set reads the same way: what it does, how to run it, and how it fits the rest. One library instead of a stack of vendor manuals.

Start with the product you are weighing up, or read across to see how the whole platform holds together.

How the compute engine is set up, tuned and run on your own hardware.

Working with the 528-domain-specialist model catalogue and routing it to your workloads.

Building multi-agent workflows and wiring them into your systems.

Knowledge governance, approval pipelines and the EU compliance references.

Running distributed and federated deployments across teams and regions.

Putting the development specialists to work inside your own projects.

Using the dashboard to watch, tune and steer everything in one view.

Standing up a sovereign, single-tenant company system end to end.

The substrate language behind the platform, for teams who want the detail.

Most teams read the docs in the same order: pick the product, learn how it works, plan the deployment, check it against your rules, then bring people on board. Each stop links straight to that part of docs.dweve.com.