AFFiNE for industries

Knowledge management for technical teams

AFFiNE is a collaborative workspace for technical knowledge: documents, whiteboards and tables in one place. Use it to explain a process, connect a diagram to its rationale, and hand over decisions with sources, owners and open questions. Explore illustrative workflows for six industries.

30-minute Google Meet Workflow, deployment and team fit

Illustrative workspace: Docs, tables and Edgeless

Workspace view
Project ChecklistComponent diagramDeployment diagram

Docs & tables

Project Checklist

CategoryTask 1: Planning & SetupTask 2: Requirements & AnalysisTask 3: UI/UX Design
Project PlanningDefine project scopeIdentify stakeholdersSet timelines
Requirements AnalysisGather functional requirementsGather non-functional requirementsDocument user stories
UI/UX DesignCreate wireframesDevelop prototypesDefine design system
Architecture & Tech StackChoose programming languagesSelect frameworksDesign database schema
Development SetupConfigure development environmentEstablish CI/CD pipelineSet up development servers
Backend DevelopmentDevelop core logicImplement API endpointsOptimize database queries
Frontend DevelopmentDevelop UI componentsEnsure responsivenessImplement API integrations
Testing & QAWrite unit testsPerform integration testsConduct system testing
Deployment & MonitoringConfigure production serversSet up load balancingImplement monitoring tools
Maintenance & SupportPlan for regular updatesFix post-launch issuesConduct performance monitoring
Component diagram · Edgeless
Component diagram — illustrative canvasNodes: User Interface, Authentication Service, Product Catalog, Shopping Cart Service, Order Processing, Payment Gateway, Database Service, Notification Service. Connections: User Interface to Authentication Service (IAuthService); User Interface to Product Catalog; Authentication Service to Shopping Cart Service; Product Catalog to Shopping Cart Service (IProductService); Product Catalog to Order Processing; Shopping Cart Service to Payment Gateway; Order Processing to Payment Gateway (IPaymentService); Order Processing to Database Service; Payment Gateway to Notification Service; Database Service to Notification Service (IDataStorage).
User Interface
Authentication Service
Product Catalog
Shopping Cart Service
Order Processing
Payment Gateway
Database Service
Notification Service
IAuthService
IProductService
IPaymentService
IDataStorage
Deployment diagram · Edgeless
Deployment diagramClient Desktop connects to Web Service. Web Service connects to Statements and Fund transfer in Application Server. Statements connects to Account details, and Fund transfer to Customer details, in Data Storage. Customer details connects to Account details.
Client Desktop
Web Service
Statements
Fund transfer
Account details
Customer details
Application ServerData Storage
Illustrative workspace — synthetic content, not a product screenshot or a customer case study. In Edgeless: drag objects, use Hand to pan, or Ctrl/⌘ + scroll to zoom. Drawing tools are visual references.

Industry solutions

Technical documentation for your industry.

Six industries, four example workflows each — suggested uses shown with synthetic examples, not customer case studies.

  1. Process, quality & engineering teams

    Manufacturing

    Document setup steps and exceptions alongside the diagrams that explain them.

    Work
    Visual work instructions · Root cause analysis
    Output
    SOPs, process diagrams and improvement notes
    Explore manufacturing workflows
  2. Solution, delivery & support teams

    IT Services

    Carry configuration details and design decisions from delivery into support.

    Work
    IT documentation · Software architecture
    Output
    Architecture notes, delivery checklists and an IT knowledge base
    Explore IT services workflows
  3. Research analysts & leads

    Investment Research

    Trace the thesis to its sources and record what could change your view.

    Work
    Investment memos · Investment thesis reviews
    Output
    Research notes, source references and a company map
    Explore investment research workflows
  4. Engineering & documentation teams

    Defense

    Give reviewers the interface assumptions, alternatives and ownership questions.

    Work
    Engineering documentation · Design reviews
    Output
    Interface notes, review records and decision rationale
    Explore defense engineering workflows
  5. Security research & consulting teams

    Cyber Security

    Connect observed behavior to assumptions and the evidence still needed.

    Work
    Threat model diagrams · Incident reviews
    Output
    Security findings, trust boundaries and follow-up notes
    Explore cyber security workflows
  6. Exploratory · engineering teams

    Aerospace

    Compare alternatives and record missing evidence in an illustrative workspace.

    Work
    Engineering design reviews · Trade study notes
    Output
    Concept diagrams, option comparisons and test observations
    Explore aerospace workflows

From example to evaluation

Find the right starting point for your team.

Discuss your documentation workflow, deployment requirements and next steps.

Book a demo

Choose a time with the AFFiNE team.

One connected workspace

Docs, whiteboards and tables. Together.

The same building blocks sit behind every industry workflow.

  • Illustrative example

    Docs for technical documentation

    Write procedures and research notes with headings, images and references.

    Explore Docs
  • Illustrative example

    Whiteboards for process and system diagrams

    Draw the sequence, components or relationships your document explains.

    Explore Edgeless
  • Illustrative example

    Tables for owners and follow-up actions

    Record open questions, assign owners and update status with your team.

    Explore Teamhub
  • Illustration of switching a doc between page and canvas mode

    Page and canvas, one doc

    Switch a doc between page and Edgeless mode.

    See how it works
  • Edit together

    Shared team workspaces with real-time co-editing.

    See team workspaces

Browse by task

Find your documentation workflow.

If your work crosses sectors, follow the example closest to it.

Common technical tasks, what teams produce, and the AFFiNE features involved
TaskTypical outputHow teams use AFFiNESee the example
Create process documentationWrite an SOP with steps, images and exception notes, then map the sequence.Step-by-step page with a sequence diagramDocs with image blocks; Edgeless for the sequence; a table for exceptions
Document system architectureDraw components and interfaces, then explain the design decisions.Architecture or interface map with decision notesEdgeless canvas next to a page that explains the choices
Review research and evidenceLink sources and counterarguments to a thesis, finding or design choice.Thesis, threat-model or trade-off record with open questionsDocs with references and PDF previews; a relationship map; a status table kept by hand
Prepare a handoverLink operating procedures, diagrams and open questions for the receiving team.Handover page linking context, decisions and open itemsShared team workspace, real-time co-editing, Markdown export

One workflow, end to end

Build a design review from notes, diagrams and decisions.

One design review, kept as a page, a whiteboard and a table — then built up in four steps by the team.

Illustrative workflow · synthetic content

Page

Data interface — design review

Purpose
Agree how two systems exchange readings
Marker 1: Decision so far
Keep the current message format for v1
Marker 2: Next step
Confirm who owns retries before handover

Edgeless whiteboard

Data interface — design review — illustrative canvasNodes: Source system, Interface, Consumer, Format v1, Who owns retries?. Connections: Source system to Interface (sends); Interface to Consumer (reads); Format v1 to Interface (defines); Who owns retries? to Format v1.
Source system
Interface
Consumer
Format v1
Who owns retries?
sendsreadsdefines12

Table · kept by the team

Open items for the example design review
ItemStatusOwner
Field mappingReviewedIntegration
Marker 2: Retry ownershipOpenTo confirm
Marker 3: Handover notesDraftingDelivery
  1. The decision written in the page is the format drawn on the canvas.
  2. The open question on the canvas is a row the team tracks by hand.
  3. Handover notes pull the page, the map and the open items together.

Numbered markers show where one view refers to another. The team makes these links by hand — nothing is synchronized or approved automatically.

  1. Capture context

    Write a review page for purpose, assumptions and decisions.

    Input: Notes and specs Output: Review brief

  2. Map relationships

    Draw the systems on the whiteboard; mark assumptions and questions.

    Input: The brief Output: Relationship map

  3. Track open questions

    Keep them in a table the team updates by hand.

    Input: Canvas questions Output: Open-questions table

  4. Hand it over

    Link brief, map and table in one page; edit together; export Markdown.

    Input: Brief, map, table Output: Handover pack

Deployment and evaluation

Run it your way.

Decide how you will run AFFiNE before you scale it.

Illustration of a hosted cloud workspace

Hosted workspace

Try one workflow with permitted sample material before you scale it.

  • AFFiNE web app
  • One team workspace
  • No servers to run
Discuss cloud deployment
Self-host AFFiNE

Prerequisites

1 / Docker

Install Docker and Docker Compose on your machine.

2 / Download the latest Compose file

Download compose.yml from the AFFiNE repository.

3 / Prepare the environment file

Review the environment variables for your deployment.

Self-hosted

Docker Compose is the officially supported path for running AFFiNE on infrastructure you operate.

  • Docker Compose
  • PostgreSQL
  • File or S3 storage
  • OIDC sign-in

Before a pilot, settle four things

  1. Who writes, reviews and reads
  2. Who runs infrastructure and backups
  3. Whether AI stays off — or which provider
  4. Which plan features you need

Local-first editing does not make every team feature work offline. An installable license for restricted networks does not make the whole product air-gapped. Self-hosting gives you control of where data lives; it does not establish compliance on its own.

Product references: AFFiNE Enterprise and documentation in English for Docker Compose, OIDC sign-in and AI configuration.

Resources

Start with a template.

Existing AFFiNE templates and guides that match the work above.

FAQ

Questions teams ask.

What should an internal knowledge base for technical teams include?

An internal knowledge base should connect procedures, system context, decisions and source references, with a named owner and review date for each page. Organize it around questions the team needs to answer. In AFFiNE, link written explanations, diagrams and follow-up tables so a new teammate can find and continue the work.

How do documents and whiteboards work together?

A page holds the written detail: purpose, assumptions, decisions and sources. The Edgeless canvas shows how the pieces relate, such as systems, steps or arguments. Teams place the diagram next to the explanation and link between them, so a reviewer can read the reasoning and see the structure in the same workspace.

Can teams use AFFiNE alongside their existing engineering or operational tools?

Yes. AFFiNE is a place to explain and connect work, not a replacement for systems of record such as production, ticketing, security monitoring or market-data tools. Teams typically link to those systems and summarize what matters for a review or handover. Check any specific integration you rely on before planning around it.

Can AFFiNE be self-hosted?

Yes. Docker Compose is the officially supported self-hosting path, and sign-in can use your identity provider via OIDC. AI features are optional and can be turned off. Review the Enterprise page and documentation with the people who will run the service, and test backup and restore in your own environment.

How should we evaluate AFFiNE for sensitive technical knowledge?

Start with the workload rather than the tool. Decide what material may be stored, where it must live, who needs access and whether AI may be used. Then compare hosted and self-hosted options against those requirements. Hosting location alone does not establish approval for a workload; involve your security and compliance owners early.

Where should a team start with a pilot?

Pick one real workflow, such as a design review or a handover, and a small set of material you are permitted to use. Build the page, the canvas and the open-questions table with the people who will maintain them. Judge the pilot by whether the next person can find, understand and continue the work.

A conversation about your team

Evaluate AFFiNE for your team.

Discuss your documentation workflow, deployment requirements and next steps.

30-minute Google Meet · Choose an available time

Prefer email? Contact sales