Flow website screenshot

Flow

Flow (Flow Engineering, operated by TRC Space Ltd) is a requirements-management platform built for hardware and systems engineering teams. It centers on a Systems Graph that connects requirements, design artifacts, tests, and components, with AI agents that continuously align CAD, simulation, code, and test — automating impact analysis, budget tracking, and compliance checking. Flow supports branching and merging of requirement baselines, iterative build gates, and an integration ecosystem spanning CAD (Onshape, Fusion 360, Siemens NX), simulation (Ansys), and dev tools (GitHub, GitLab, Jira, Linear, Slack, Notion, Confluence). It is SOC 2 Type II, NIST 800-171, and ITAR/EAR aligned with self-hosted and AWS GovCloud options. A first-party API exists (referenced in the changelog) but is gated behind login with no publicly published OpenAPI or developer documentation.

Flow is profiled on the APIs.io network. Tagged areas include Company, Requirements Management, Systems Engineering, Hardware Engineering, and Product Lifecycle Management.

Flow’s developer surface includes documentation, pricing, signup flow, support, changelog, and 10 more developer resources.

21.4/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
0 APIs
CompanyRequirements ManagementSystems EngineeringHardware EngineeringProduct Lifecycle ManagementEngineeringComplianceAI Agents

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 21.4/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 2.6 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/flow: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Flow Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Flow Trust Center

SOC 2 Type II, NIST 800-171, ITAR/EAR, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: flow
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/flow.png
name: Flow
description: Flow (Flow Engineering, operated by TRC Space Ltd) is a requirements-management platform built for hardware and
  systems engineering teams. It centers on a Systems Graph that connects requirements, design artifacts, tests, and components,
  with AI agents that continuously align CAD, simulation, code, and test — automating impact analysis, budget tracking, and
  compliance checking. Flow supports branching and merging of requirement baselines, iterative build gates, and an integration
  ecosystem spanning CAD (Onshape, Fusion 360, Siemens NX), simulation (Ansys), and dev tools (GitHub, GitLab, Jira, Linear,
  Slack, Notion, Confluence). It is SOC 2 Type II, NIST 800-171, and ITAR/EAR aligned with self-hosted and AWS GovCloud options.
  A first-party API exists (referenced in the changelog) but is gated behind login with no publicly published OpenAPI or developer
  documentation.
url: https://raw.githubusercontent.com/api-evangelist/flow/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- lightspeed-venture-partners
- seedcamp
- version-one-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Requirements Management
- Systems Engineering
- Hardware Engineering
- Product Lifecycle Management
- Engineering
- Compliance
- AI Agents
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://flowengineering.com
- type: Documentation
  url: https://flowengineering.com/handbook/iterative-systems-engineering/volume-1
- type: Pricing
  url: https://flowengineering.com/pricing
- type: SignUp
  url: https://app.flowengineering.com/sign-in
- type: Login
  url: https://app.flowengineering.com/sign-in
- type: Support
  url: mailto:contact@flowengineering.com
- type: Integrations
  url: https://flowengineering.com/integrations
- type: ChangeLog
  url: https://flow-engineering.productlane.com/changelog
- type: ChangeLog
  name: Flow changelog (harvested)
  url: changelog/flow-changelog.yml
- type: PrivacyPolicy
  url: https://flowengineering.com/privacy-and-cookie-policy
- type: Careers
  url: https://flowengineering.com/careers
- type: Compliance
  url: https://flowengineering.com/security
- type: TrustCenter
  url: security/flow-trust-center.yml
- type: DomainSecurity
  url: security/flow-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/flowengineer/
- type: Twitter
  url: https://x.com/Flow_Engineer
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence