Stellarbridge Docs

Documentation

About stellarbridge

stellarbridge was built for the reality that regulated organizations face today: sensitive data moving across organizational boundaries under the weight of compliance requirements, audit obligations, and real liability. The platform is purpose-built for that environment — with policy-first controls, chain-of-custody audit trails, and deployment flexibility for demanding security programs.

We serve teams in defense, healthcare, government, and critical infrastructure, where the cost of getting data governance wrong is measured in fines, lost contracts, and damaged trust. stellarbridge gives compliance and security teams visibility and control over how data moves, so they can meet their obligations and prove it.

You may see stllr used as internal shorthand for stellarbridge.

Who it’s for

  • End users — Send and receive files, use the Drive, and work with shared links.
  • AI agents — Access objects and data for context, or to send and receive from other workflows.
  • Admins — Configure organizations, policies, roles, and access.
  • Compliance and security — Audit trails, export logs, and compliance evidence.

What is stellarbridge?

stellarbridge is a governance and transfer platform for sensitive data. It lets users and organizations move files across boundaries — between teams, partners, and locations — with policy enforcement, audit trails, and the deployment options (cloud or self-hosted) that regulated environments require.

We are building toward a control plane for how data moves as more of that movement is initiated by AI systems and automated workflows. stellarbridge is focused on giving compliance and security teams the same visibility and control over machine-driven data flows that they expect over human-driven ones — the proof layer that governance didn’t break when the agents showed up.

Core concepts

Moving data

  • File uploads — Send files to a destination (person, team, folder) for quick or governed transfers.
  • File streaming — Send large files with resume support; better for unreliable networks.
  • Transfers — A transfer is an upload or stream instance; you can protect it, lock it to the org, or generate a custody report.
  • Transfer requests — Create a request and share an upload link; the recipient uploads without logging in.
  • Public links — Recipients use links to download (transfer or drive share) or upload (to fulfill a request); no account required.

Drive and structure

  • Drive — Where governed files and folders live. You browse by project, upload and download, attach policies, and generate custody reports. See Using the Drive.
  • Projects — Top-level containers in the Drive. A project is either partner-scoped (one or more partners) or organization-only (no partners, tied to the org). Internal work can use org-only projects.
  • Partners — External organizations or parties you share with or receive from. Policies can live in the organization catalog or under a partner catalog; projects can be scoped by partner or be org-only.

Governance

  • Policies — Access policies (YAML or JSON) define who can do what on drive objects: list, download, send, delete, share, and more. Effects are ALLOW, DENY, or GATE (require admin approval).
  • Roles (RBAC) — Role-based access control decides which API routes and dashboard areas a user can use. Policies apply only after the user has passed RBAC.
  • Identities — Users (UPN), API keys (API), and agents (AGENT) are identities; policies match on identity type, email, or group.
  • Groups — Named sets of identities used in policies (e.g. “readers”, “editors”) so you don’t list individuals.

Organization and access

  • Organization — Your tenant: users, invites, org settings (SAML, password rules, lock-to-org), and audit scope. See Managing your organization.
  • Gate — When a policy uses the GATE effect, an admin must approve the action (e.g. via a one-time link in email) before it proceeds.

Audit and compliance

  • Audit logging — Security-relevant events (auth, transfers) are recorded; you can view them in the dashboard or export to a SIEM. Chain-of-custody reports are available for transfers and Drive objects.

Next steps