Exploring AFFiNE for Aerospace

Engineering design reviews for aerospace teams.

A trade study compares design alternatives against explicit criteria and documents the evidence, assumptions and uncertainty behind the choice. Use AFFiNE for option tables, concept diagrams and review notes. Engineering calculations, controlled configurations and certification evidence remain in the specialist systems approved for that work.

30-minute Google Meet Workflow, deployment and team fit

Illustrative workspace: Sensor enclosure — concept review

Workspace view
Sensor enclosure — concept reviewSystem concept noteTrade-off discussionTest observation reviewEngineering handover

Page · demonstration study · not a customer project

Sensor enclosure — concept review

Study
Generic enclosure concept
Trade-off
Access versus packaging
Next step
Review the assumptions

Assumption: service access is required. Interface space still to confirm.

Same project · Edgeless canvas
Sensor enclosure — concept review — illustrative canvasNodes: Need, Concept, A · Direct access, B · Compact, Assumption review. Connections: Need to Concept (constrains); Concept to A · Direct access; Concept to B · Compact; A · Direct access to Assumption review; B · Compact to Assumption review (evidence?).
Need
Concept
A · Direct access
B · Compact
Assumption review
constrains
evidence?
  • The generic concept under study and the need that constrains it.
  • Two options under exploration, drawn as branches rather than a verdict.
  • Both options feed the next assumption review.

Edgeless

System concept note

Sketch the concept and its interfaces, then record its purpose and assumptions. Mark unresolved constraints beside the diagram for the next design discussion.

Purpose
Generic enclosure study
Assumption
Service access required
Question
Confirm interface space
Same project · Edgeless canvas
System concept note — illustrative canvasNodes: Need, Concept, Interface, Interface space?. Connections: Need to Concept; Concept to Interface; Interface to Interface space? (to confirm).
Need
Concept
Interface
Interface space?
to confirm

Page + table

Trade-off discussion

Compare design options against explicit criteria in a table. Link sketches and supporting evidence, and record why an option needs further investigation.

Option AOption B
ArrangementDirect accessCompact arrangement
Still to showPackaging spaceService access
Next evidence

Review packaging sketch

Same project · Edgeless canvas
Trade-off discussion — illustrative canvasNodes: Need, Concept, A · Direct access, B · Compact, Assumption review. Connections: Need to Concept (constrains); Concept to A · Direct access; Concept to B · Compact; A · Direct access to Assumption review; B · Compact to Assumption review (evidence?).
Need
Concept
A · Direct access
B · Compact
Assumption review
constrains
evidence?
  • The generic concept under study and the need that constrains it.
  • Two options under exploration, drawn as branches rather than a verdict.
  • Both options feed the next assumption review.

Page + table

Test observation review

Record the setup, observations and remaining uncertainty from a permitted test activity. Link the findings to the concept notes that need another review.

  • Observed · Observation

    Example fit check

  • Uncertain · Uncertainty

    Assembly access

  • Planned · Next review

    Update concept notes

Setup → Observation → Uncertainty → Learning

Same project · Edgeless canvas
Test observation review — illustrative canvasNodes: Need, Concept, A · Direct access, B · Compact, Assumption review. Connections: Need to Concept (constrains); Concept to A · Direct access; Concept to B · Compact; A · Direct access to Assumption review; B · Compact to Assumption review (evidence?).
Need
Concept
A · Direct access
B · Compact
Assumption review
constrains
evidence?
  • The generic concept under study and the need that constrains it.
  • Two options under exploration, drawn as branches rather than a verdict.
  • Both options feed the next assumption review.

Page

Engineering handover

Link the concept, trade-off analysis and test observations in one overview. Record decisions and open questions so the next team can continue the review.

Concept
Current arrangement
Rationale
Key trade-offs
Learning
Questions to revisit

Shared workspace · edited together

Same project · Edgeless canvas
Engineering handover — illustrative canvasNodes: Need, Concept, A · Direct access, B · Compact, Assumption review. Connections: Need to Concept (constrains); Concept to A · Direct access; Concept to B · Compact; A · Direct access to Assumption review; B · Compact to Assumption review (evidence?).
Need
Concept
A · Direct access
B · Compact
Assumption review
constrains
evidence?
  • The generic concept under study and the need that constrains it.
  • Two options under exploration, drawn as branches rather than a verdict.
  • Both options feed the next assumption review.
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.

From task to workspace

From concept notes to a trade study review.

Explore how a team could document a concept, compare alternatives, review observations and prepare an engineering handover.

Task-to-feature map for the four examples on this page
TaskDocsEdgelessTablesTeamExportOutput
01 · Systems teamDocument a system conceptDocsEdgelessSystem concept note
02 · Design review teamOrganize trade study notesDocsEdgelessTablesTrade-off discussion
03 · Test knowledge teamReview test observationsDocsTablesTest observation review
04 · Engineering leadPrepare an engineering handoverDocsEdgelessTeamEngineering handover

01Systems team

Document a system concept

Sketch the concept and its interfaces, then record its purpose and assumptions. Mark unresolved constraints beside the diagram for the next design discussion.

Task
Give a concept sketch its written context
In AFFiNE
System relationship sketched in Edgeless; purpose and assumptions in the page
Output
System concept note

Features used

EdgelessSynthetic example

System concept note

System concept note — illustrative canvasNodes: Need, Concept, Interface, Interface space?. Connections: Need to Concept; Concept to Interface; Interface to Interface space? (to confirm).
Need
Concept
Interface
Interface space?
to confirm
Purpose
Generic enclosure study
Assumption
Service access required
Question
Confirm interface space
Illustrative layout with synthetic content — not a product screenshot.

02Design review team

Organize trade study notes

Compare design options against explicit criteria in a table. Link sketches and supporting evidence, and record why an option needs further investigation.

Task
Discuss a trade-off with the reasons visible
In AFFiNE
Options beside the sketch; a hand-maintained table of criteria and next evidence
Output
Trade-off discussion

Features used

Page + tableSynthetic example

Trade-off discussion

Option AOption B
ArrangementDirect accessCompact arrangement
Still to showPackaging spaceService access

Next evidenceReview packaging sketch

Illustrative layout with synthetic content — not a product screenshot.

03Test knowledge team

Review test observations

Record the setup, observations and remaining uncertainty from a permitted test activity. Link the findings to the concept notes that need another review.

Task
Keep a test observation useful afterwards
In AFFiNE
Observation page with a table separating what was seen from what is uncertain
Output
Test observation review

Features used

Page + tableSynthetic example

Test observation review

  • ObservedObservationExample fit check
  • UncertainUncertaintyAssembly access
  • PlannedNext reviewUpdate concept notes

SetupObservationUncertaintyLearning

Illustrative layout with synthetic content — not a product screenshot.

04Engineering lead

Prepare an engineering handover

Link the concept, trade-off analysis and test observations in one overview. Record decisions and open questions so the next team can continue the review.

Task
Carry the context into the next project
In AFFiNE
Handover page linking concept, trade-offs and lessons; the canvas shows how they relate
Output
Engineering handover

Features used

PageSynthetic example

Engineering handover

  1. ConceptCurrent arrangement
  2. RationaleKey trade-offs
  3. LearningQuestions to revisit

Shared workspace · edited together

Illustrative layout with synthetic content — not a product screenshot.

From example to evaluation

Explore a fit for your engineering team.

Discuss concept notes, trade study documentation and the scope of an initial evaluation.

Book a demo

Choose a time with the AFFiNE team.

One connected workspace

Write in a page. Switch the same doc to a canvas.

The examples above use the same building blocks.

  • Illustrative example

    Docs

    Readable pages with references, images and rich blocks.

    Explore Docs
  • Illustrative example

    Edgeless whiteboard

    A canvas to show how ideas and systems relate.

    Explore Edgeless
  • Illustrative example

    Tables and team workspace

    Track what is open and edit together in shared spaces.

    Explore Teamhub

Illustrative examples of docs, whiteboards and tables — not product screenshots or industry case studies.

Deployment and evaluation

Choose how the workspace runs.

Evaluate the workload, infrastructure and AI configuration together, with the people who will operate the workspace.

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

For self-hosted AFFiNE, Docker Compose is the documented deployment path. Workspace data and uploads use the infrastructure and storage you configure.

  • Docker Compose
  • PostgreSQL
  • File or S3 storage
  • OIDC sign-in
  • Sign in through your identity providerSelf-hosted AFFiNE supports OIDC. Review workspace roles and document access against your own requirements.
  • AI is optionalSelf-hosted AI needs a configured provider and can be turned off. Bring-your-own-key is marked experimental.
  • Licensing for restricted networksAn installable license activates without calling AFFiNE’s license servers. That alone does not make every feature work offline.
  • Backup and restoreThe process is documented, including a test restore. Run it in your own environment.
  1. Which engineering notes are suitable for a first pilot?
  2. Where does the workspace need to run?
  3. Which formal systems remain authoritative?

This page makes no claim about SAML, SCIM, industry certifications, or approval for any specific workload.

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

Continue exploring · AFFiNE product page

AFFiNE Edgeless

See how a canvas and written pages share one workspace.

Before you start

Questions from your team.

How can we document a trade study in AFFiNE?

Record the decision to be made, alternatives, comparison criteria, supporting evidence and uncertainty. If your team uses weights or scores, document how they were chosen. Link concept diagrams and note what would trigger a reassessment. AFFiNE holds the working explanation; calculations and formal engineering decisions remain with your team and specialist tools.

Engineering reference (English): NASA Systems Engineering Handbook: decision analysis.

Is this an aerospace customer case study?

No. This is an illustrative workspace for evaluating a possible use. It does not describe a customer deployment.

Does AFFiNE replace certification or configuration systems?

No. These examples cover notes, diagrams and engineering knowledge. Keep certification evidence, controlled configurations and formal requirements in approved systems.

Can we evaluate self-hosting?

Yes. Docker Compose is the documented self-hosting path, with sign-in through your identity provider via OIDC. Review the Enterprise documentation with your infrastructure team, then test one representative workflow before a wider rollout.

Is AI required for this workspace?

No. These workflows use pages, canvases and tables without requiring AI. In self-hosted AFFiNE, AI needs a configured provider and can be turned off. Review the provider and data flows before enabling it.

How should our team start?

Choose one current documentation task and a small set of permitted sample material. Evaluate whether the team can find, understand and hand over the work before expanding.

A conversation about your team

Discuss your engineering evaluation.

Discuss concept notes, trade study documentation and the scope of an initial evaluation.

30-minute Google Meet · Choose an available time

Prefer email? Contact sales