Atlas Mission SDK
Integrate software with the Atlas application and its Mission data model.
Use Atlas Mission SDK to publish sensor observations into Atlas or consume them in external software. Mission supplies the application's Tracks, sites, assets, reports, organizations, Groups, and teams.
Choose the product
| Your goal | Start here |
|---|---|
| Build an independent peer application with your own schema and authority | Platform SDK |
| Publish or consume Atlas Tracks and telemetry | Tracks |
| Create a site that appears in Cache Management | Entities and placement |
| Run an organization's persistent synchronization peer | Atlas Gateway Fabric |
Mission supplies domain rules. Platform supplies identity, storage, replication, event delivery, streams, and networking. Mission does not replace those mechanisms with a separate transport stack.
Learn the Mission model
Choose the concept that answers your next integration question:
| Question | Chapter |
|---|---|
| Which identity signs, and how does it join? | Identity and admission |
| Which organization, Group, and team owns the data? | Organizations, Groups, and teams |
| Which object represents a site or asset? | Entities and placement |
| How do saved Tracks differ from observations? | Tracks |
| What do detection and telemetry payloads mean? | Events and telemetry |
| How do I store structured reports or adapter status? | Schemas, documents, and ontology |
Find details without changing products
Mission reference groups domain methods and types. Errors, security, and compatibility covers integration boundaries.