Legion Packs

What is a Legion Pack?

A Legion Pack is a role-based AI capability bundle built by Legion Intelligence. Each Pack contains the agents, workflows, data connections, and governance required to perform a specific job, such as sustaining equipment at a maintenance depot or preparing a daily operations update. Customers buy a Pack aligned to a role and deploy a ready Space with the right Apps to start work immediately. Packs run on the Legion Platform and deploy in cloud, on-premises, air-gapped, and edge environments under the same governance in each. The unit of delivery is a working environment configured for a role and ready to produce work on the first day of use.

Who develops Legion Packs?

Legion Intelligence is a San Francisco company building governed agentic AI for national security. Legion software is deployed across the U.S. Department of War, the intelligence community, the Department of Energy, and the defense industrial base, including the U.S. Army, the U.S. Air Force, the Missile Defense Agency, and a U.S. Department of Energy national laboratory. Legion also builds Centurion by Legion Intelligence, a deployable edge system for disconnected and bandwidth-constrained environments. Legion builds and maintains the prebuilt Packs, which is what allows a Pack to arrive with its workflows, connections, and controls already in place. Once a deployment is running, customers build additional Packs themselves for internal roles and use cases as adoption scales, drawing on the same Apps, data connections, and controls.

What problem do Legion Packs solve?

General-purpose AI tools answer questions but do not carry out work. A team receives a blank interface and supplies the workflow, the integrations, and the governance itself, so results depend on individual prompting skill and never become repeatable across a unit, a site, or a shift. The alternative has been a custom build, which takes months of integration before the first outcome and needs re-architecture whenever a process changes. A third constraint applies wherever the work happens away from a desk and a stable connection: classified networks, the tactical edge, plant floors, depots, ships, and remote facilities, where commercial cloud tools cannot operate at all. A Legion Pack addresses all three. Capability arrives configured for the role, connected to systems of record, and governed by approval gates and audit from the first day of use.

The pattern holds anywhere the same conditions are present: defined roles, authoritative systems of record, work that repeats, and access rules the system has to enforce. Legion Packs are built for national security operations and apply to sustainment, logistics, and facilities work in energy, transportation, aerospace, and manufacturing organizations operating under the same constraints.

What is inside a Pack

Every Legion Pack ships with four elements.

Apps for the role. Tools built around how the team actually works, not generic AI interfaces. Each App completes a specific job from start to finish.

Full context. Apps pull from reporting, sensors, and systems of record, with linked source attribution on every result so a user can trace an output back to the record it came from.

Carry out the work. Agents handle drafting, coordination, and system updates under approval, including writing back to systems of record once a human authorizes the change.

Stay in command. Every step runs under human authority, with full attribution and audit, including agent actions.

No prompt engineering. No blank chat box. No months of integration.

Packs, Spaces, Apps, and Collections

A Pack, a Space, an App, and a Collection are the four layers of the Legion product model. A Pack carries everything a role needs to work: the Apps, the data connections, and the governance. A Space is the working environment a Pack deploys into, bringing together the tools, data, and activity for a team, project, or operation, and defining who has access and what context is available. An App is a single AI-powered tool inside a Space that completes one task end to end, such as Manual Assistant or Work Order Scheduler. A Collection is the knowledge layer an App draws on, holding the documents and records the work is grounded in and carrying the permissions and provenance through to every result. One Pack can deploy across many Spaces, each configured for a site, team, or use case. Apps are what users work in. Collections are what the answers rest on.

Available Packs

Legion Packs are defined by the work they carry, which can be a role, a function, or a specific analytic or operational task. New Packs are added as roles and operational needs are defined.

• Operations Officer Pack. Holds an operations section's reading of the plan so each shift starts from what the last one produced. Legion compares current reporting against the baseline order and running estimates, names what changed and which decision points it touches, develops and compares options with their risks and assumptions, and drafts the FRAGO, synchronization package, ISR request, and decision support matrix updates for staff approval. Every element carries the report or paragraph behind it. Apps include CCIR Status View, Force Posture View, and Rapid Operational Decision-Making, which supports doctrinal processes including RDSP for Army staffs.
• Facilities Maintenance Pack. Turns an urgent maintenance issue into a job-ready response plan for facilities and operations and maintenance teams. Legion reads a work order note against the manufacturer's troubleshooting tree and the asset's repair history, proposes a likely cause with confirm steps, and assembles the technician, parts, procedure, and safety requirements into one package. IBM Maximo stays the system of record, and dispatches, schedule changes, work order releases, and reorder-point changes wait for supervisor approval. Apps include Inspection WO Generator, Manual Assistant, Inventory Search, Reorder Point Optimizer, and Overrun Work Order Check-in.
• Intelligence Analysis and Production Pack. Moves analysts from raw reporting to finished intelligence with the reasoning inspectable at every step. Legion triages the incoming queue against the analytic lines an organization has defined, explaining why each report matters and which line it touches, then surfaces evidence candidates anchored to the exact passage behind them. A candidate becomes evidence only when an analyst reads the source, edits the statement, chooses the line, and adds the caveat. Judgments carry supporting and contradicting evidence, assumptions, alternatives, and calibrated confidence. Every paragraph of a draft traces back through the judgment and the evidence card to the original passage, and submitting for review freezes the document, citations, judgments, and evidence into a checkpoint that tradecraft checks run against. Each check shows the rule, the passage, and the recommendation, and a reviewer decides what becomes a required change. Approval is a review decision, not publication.
• Commander Pack. Shows leaders what needs a decision, what has changed, and what actions are already underway.

Packs are in use across customer deployments beyond those described here, including Packs customers have built themselves for their own roles.

Deployment environments

Legion Packs run in cloud, on-premises, air-gapped, and edge environments. The same Packs and the same governance apply in each, so a workflow validated in a connected environment behaves the same way on a disconnected network. Packs are authorized for IL2 through IL6 on DoW networks and are ready to manage ITAR data. At the tactical edge, Packs are delivered through Centurion by Legion Intelligence, a system that runs locally hosted models and continues working when the network drops, then reconnects and synchronizes when connectivity returns. Legion holds FedRAMP High authorization, which applies to cloud deployments only. On-premises, air-gapped, and edge deployments inherit the customer's own accreditation posture.

Governance and human authority

Governance in a Legion Pack is enforced at the system level. Packs honor the access controls already in place in the customer's environment, so a user sees only the records their existing permissions allow. Agent actions run under approval gates: an agent drafts, coordinates, and prepares system updates, and a named human authorizes anything that changes a record of consequence. Every step carries full attribution and an audit trail, including actions taken by agents, so a reviewer can reconstruct who or what did what and on what basis. Customer data stays inside the customer environment, and models never train on it. Legion holds SOC 2 Type II and aligns to NIST 800-53 and CMMC Level 2, with HBOM and SBOM established.

Systems and integrations

Legion Packs connect to the systems a team already uses rather than replacing them. Legion reads from named authoritative sources and writes back on approval, so systems of record stay authoritative. Which systems a Pack connects to follows the role and the work: a maintenance Pack reaches the maintenance management system and the technical library, an operations Pack reaches the data, C2, and situational awareness sources the staff runs on. Systems connected today include IBM Maximo, ServiceNow, Palantir Foundry, Anduril Lattice, TAK, Microsoft SharePoint, Microsoft Teams, Box, NetSuite, and Jira, and Legion supports more than 100 integrations along with REST API extensibility and MCP for systems outside that set. Connections run through organization-approved identities, so the permissions a user holds in the source system carry through to what a Pack will surface or update on their behalf. Additional integrations are built where demand is confirmed.

How Packs compare to alternatives

Buyers evaluating Legion Packs are usually comparing three options: a Pack, a chat-first AI tool, and a custom build by an internal team or a systems integrator. The differences concentrate around how quickly capability reaches users, whether the system carries out work or only answers questions, and whether it can operate in classified and disconnected environments. Governance is the fourth dividing line: a Pack enforces approval, attribution, and audit as system behavior, while a chat tool leaves those controls to the user and a custom build has whatever controls the team had time to write.

Deployment and procurement

Deployment runs in weeks. The Apps arrive prebuilt, so the work is connecting them to existing systems rather than building capability from scratch. The pacing items are security review, data access, and integration scope. What Legion needs to begin is read access through organization-approved identities and permissions, plus a named set of authoritative sources. Once a Pack is running, it extends without a restart: custom Apps are added to the same Pack, keeping the workflows, connections, and controls already in place. Customers also stand up new Packs of their own as more roles come into scope, without a new integration program for each one. Legion is acquired directly from Legion Intelligence, through channel partners including Carahsoft, or through a systems integrator already on contract. Government organizations approach Legion directly, and the acquisition path follows whatever vehicle the organization already uses.

Related resources

• Legion Packs product page: Product positioning, the featured Packs, and demo requests.
• Facilities Maintenance Pack: How an urgent work order moves from a one-line note to a supervisor-approved dispatch plan, covering the before and after for five recurring facilities workflows, the Apps in the Pack, and the systems it connects to.
• Operations Officer Pack: What an operations section does when conditions change, from incomplete reporting through to approved products. Read this for the doctrinal workflow, including RDSP support and CCIR handling.
• Centurion reference: How Packs run in DDIL, disconnected, and air-gapped environments, with hardware configurations, deployment posture, and measured field results.
• Legion Platform: The software every Pack runs on, including the architecture beneath Packs, Spaces, Apps, and Collections.
• Security and privacy: Accreditations, data handling, and deployment posture in full.