Skip to main content

The Soldier-Developer Concept

What Is a
Soldier-Developer?

The Army's platforms already give you the tools to build software. This is the story of how that happened, what it means, and why you are part of something bigger than your unit.

The Army's Data Platforms Did Something No One Fully Expected.

Over the past decade, the Army fielded powerful digital platforms across the force, Army Vantage and GenAI.mil among them. These platforms were designed to improve data analysis and decision-making. But they did something their designers did not fully anticipate.

These platforms gave you built-in tools to create your own software, including AI agents. The Army no longer has to depend almost entirely on outside contractors to build software. You can now build tools inside approved Army platforms.

In the past, fielding any new Army software meant navigating a lengthy cybersecurity accreditation process, the Authorization to Operate, that could take months or years. Because these platforms are already accredited, the tools built inside them inherit those approvals automatically. No separate reviews or long waiting periods. You can build and deploy today.

Definition

A soldier-developer is not a software engineer. Their role is to create practical problem-solving tools to address local unit and operational needs, from automating a tedious planning task to building an AI agent for wargaming.

You are not building major Army systems from scratch, you are using approved tools inside approved systems to solve real problems quickly. That distinction matters, it means you don't need a computer science degree or know how to write lines of code. All you need to be a soldier-developer is a problem worth solving and the willingness to learn how these platforms work.

Soldier-Developer vs. Software Engineer

Soldier-Developer

Solves Problems

  • Builds tools inside Army-approved platforms
  • Solves local unit and operational problems
  • No coding or CS background required
  • Inherits existing security approvals automatically
  • Deploys immediately to their unit
VS

Software Engineer

Builds Systems

  • Writes and maintains production code
  • Builds major Army programs from scratch
  • Requires computer science background
  • Works through formal acquisition processes
  • Develops for enterprise-scale deployment

The platforms are already approved, and you already have access.

You do not need to request new software, wait for a contract, or navigate an accreditation process. The platforms below are already fielded, already approved, and already available to you. Building starts now.

Army Vantage

Palantir · Enterprise Platform

Army Vantage is an enterprise data platform fielded across the force. It provides data access, built-in AI tools, and a no-code environment for building and deploying agents. All four agents on this site were built inside Army Vantage.

Powerful and data-rich, but has a steeper learning curve. Built on Palantir's data platform and connected to Maven Smart System, it gives your agent access to refined, large-scale Army data. The tradeoff: it takes more time to learn and master.

GenAI.mil

Department of War · AI Platform

GenAI.mil is the Department of War's official generative AI platform, providing access to large language models inside a secure, approved environment. It gives you the ability to build and deploy AI agents without leaving the approved ecosystem.

Easier to get started and more accessible for first-time builders. Agentic capability is more limited than Army Vantage since it operates without access to the same volume of refined data, but it is the faster path to your first deployed agent.

The best tool wins, regardless of who built it.

As more soldiers build tools, the Army is creating something new: an internal competition in which the best solutions rise through actual use. A private's tool can displace a colonel's if it works better and people adopt it. Rank does not determine value, results do.

Three natural forces sort good tools from weak ones without central management. Soldiers rotate frequently, so tools that only one person can maintain disappear when their creator leaves. Competing duties drive out tools that require constant upkeep. And when multiple soldiers tackle the same problem, better solutions displace weaker ones. A tool that survives all three pressures has already proven its worth under real conditions.

This departs from the traditional model, where the Army predicted its software needs and funded development in advance. That made sense when building software required scarce specialists and expensive infrastructure. Army-approved platforms change the math. When soldiers can build tools inside existing, approved environments at low cost, the Army can observe actual usage rather than predict it.

"

If the Army leverages its volume of soldier-developers to conduct bottom-up innovation and experimentation at the local level, it can scale valuable software tools and become one of the world's largest software developers.

LTC Anthony A. Joyce · War on the Rocks, March 2026

You start at Level One, but your tool can go further.

You start in the same place every soldier-developer does: building a tool inside an approved platform to solve a real problem. That is Level 1, and it is where this site focuses. But if your tool works and people use it, it has a path upward. The Army is building the infrastructure to identify, support, and scale what the force actually adopts.

02
Path Upward

Army-Level Support

Tools that prove their value through real, sustained use get noticed. The Army is building the infrastructure to surface these tools, give them a named organizational owner, and provide the engineering resources to keep them running after their original builder has moved on. The force decides what rises through usage data, not applications or endorsements.

03
Path Upward

Enterprise Integration

A small number of proven tools will warrant Army-wide use. Before the Army approves a new software purchase, it checks whether a soldier-built tool already solves the problem. The best tools built at the unit level become Army capabilities. Not because someone championed them up the chain, but because the force already proved their worth.

You are already a Soldier-Developer, you just haven't built yet.

The platforms are approved and already available to you. The only thing missing is your first agent. Start with a problem your unit actually has.