> ## Documentation Index
> Fetch the complete documentation index at: https://datarelay.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Design Philosophy

> Shared design principles across DataRelay Labs projects.

# Design Philosophy

DataRelay Labs projects are independent, but they share a small set of practical engineering principles.

<CardGroup cols={2}>
  <Card title="Solve field problems first" icon="wrench">
    Start from recurring connectivity, delivery, support, and operations problems instead of adding features for their own sake.
  </Card>

  <Card title="Relay only what is needed" icon="filter">
    Avoid opening entire networks or duplicating full data flows when a narrow, controlled path can solve the actual requirement.
  </Card>

  <Card title="Keep products independent" icon="boxes-stacked">
    A user should be able to adopt one product without installing another. Runtime, release lifecycle, and documentation remain separate.
  </Card>

  <Card title="Make boundaries explicit" icon="shield-halved">
    Document prerequisites, security assumptions, supported paths, limitations, failure handling, and recovery instead of hiding operational constraints.
  </Card>
</CardGroup>

## Organization model

`datarelay.run` is the **DataRelay Labs organization portal**. Product documentation belongs on dedicated product sites such as `link.datarelay.run` and `control.datarelay.run`.

This keeps the top-level domain stable as the project family grows and lets future products join the organization without being presented as modules of an existing product.

<Card title="DataRelay Labs on GitHub" icon="github" href="https://github.com/datarelay-labs">
  Browse source repositories and engineering work across the organization.
</Card>