Strengthening space domain awareness through Guardian-led software

The Challenge

Space is no longer a wide-open frontier. Thousands of satellites, growing fields of debris, and adversary assets have turned orbit into a high-stakes environment where speed and precision are a matter of national security.

A Guardian-led operations team plays a key role in maintaining this security in space. Aligned under a key operational unit for mission execution and the Air Force Research Laboratory (AFRL) for research and development, the team supports the U.S. Space Force’s SDA mission and the advancement of SDA technologies by tracking, monitoring, and cataloging resident space objects (RSOs) to support space traffic management, collision avoidance, and threat detection, while experimenting with new ways to improve mission execution.

They operate mission-critical assets and systems, including high-powered optical tracking systems and research-focused assets used for experimentation. They also support advanced computing efforts through a high-performance computing center, where research teams look at new ways to analyze and process tracking data. Balancing daily mission execution with long-term innovation creates natural competition for telescope access, making scheduling a persistent challenge.

Unlike earlier efforts that primarily tracked objects, today’s SDA requires insights into what those objects are doing, how they behave, and what threats they might pose. That awareness depends on uninterrupted observations, fast decision-making, and the ability to pivot priorities in real time.

The unit had the mission and the talent to deliver on this awareness, but was working with legacy tools that made all of that harder to do:

• Fragmented data sources and decentralized notifications required operators to monitor multiple sources for schedule changes, leading to missed updates and delayed conflict resolution.
• Staffing conflicts and resource allocation problems caused observation cancellations when manual verification processes missed certification requirements or availability issues.
• Leadership lacked timely access to operational data, limiting their ability to evaluate mission performance or secure necessary resources.
• Disconnected PTO and certification tracking created staffing blind spots, leading to missed observations and lost SDA opportunities.

Each missed data collection window created a gap in space traffic monitoring and threat detection. A single oversight, like an overlooked certification check, could leave a telescope offline during key observation windows, forfeiting valuable data and triggering last-minute staff reassignments. As more nations and commercial actors deploy assets in orbit, those inefficiencies escalate into national security risks and global space instability.

The organization needed a better way to schedule, operate, and scale that legacy tools and traditional acquisition timelines wouldn’t impede.

The Approach

Instead of asking operators to work around outdated systems, we helped the unit rebuild its scheduling approach and software development processes. We enabled a new Integrated Software Squadron model that allows teams to build their mission software rather than relying on traditional, lengthy acquisition processes.

The Integrated Software Squadron model positions the unit as both an operational force and a software delivery organization. Decentralizing software creation allows squadrons to build solutions that meet their specific needs and respond quickly to threats and challenges. Software is built, operated, and maintained by Guardians, for Guardians, with the unit controlling the digital roadmap.

The first major application created through this new model was a web-based scheduling system that replaced a patchwork of SharePoint, Excel, and Word files with fast, accurate scheduling across all telescope mounts, sensors, and staffing resources.

We built the system to mirror tools Guardians already use, like Outlook and Google Calendar, so there were no steep learning curves or extended onboarding. Scheduling a telescope is now as simple as booking a meeting, with automatic conflict checks and clear visibility into shifts and staffing.

To support this delivery model, we helped the team evaluate and select infrastructure platforms to meet IL4 requirements, minimize risk, and scale efficiently. We developed the app on Platform One after assessing alternatives for compatibility, cost, and operational fit. Infrastructure decisions prioritized security, maintainability, and developer experience from the outset.

Our approach combined modern development practices with user-centered product design:

• Embedding DevSecOps principles into the development process through inherited controls, passive vulnerability scanning, test-driven development (TDD) & test automation, and hardened containers from Iron Bank. Security became part of every sprint to cut approval time and tighten system resilience without slowing delivery.
• Leading direct feedback sessions with Guardians to validate feature functionality and capture real mission needs to reduce feature bloat. Operators test recent updates, identify issues, and shape the next iteration.
• Pairing with internal developers during the initial contract to enable Guardian-led development. Documentation, embedded collaboration, and lightweight onboarding helped maintain continuity despite regular Supra Coder rotation.
• Automating scheduling conflict detection and staffing notifications to remove manual coordination. Flagging conflicts, gaps, and missed certifications in real time and sending centralized communication cleared bottlenecks before they could stall operations.
• Establishing a clear path to ongoing authorization for continuous delivery, commonly referred to as continuous Authorization to Operate (cATO), with Platform One deployment pipelines that include built-in security checks, monitoring, and production telemetry so that updates can reach production environments without bureaucratic lag.
• Creating lightweight, modular code that is maintainable despite frequent personnel rotations. Code design decisions emphasized readability, test coverage, and knowledge sharing to protect delivery continuity.
  

Approaching the challenges with this structure means the unit can take full ownership of its software delivery cycle, reduce dependency on external teams, and establish faster, more proactive SDA operations.

Outcomes

Through the delivery of the scheduling application and the Integrated Software Squadron model, Rise8 helped the unit achieve immediate and measurable improvements across scheduling, mission effectiveness, and resilience, leading to extra days of mount usage annually with enhanced continuous space monitoring capabilities and orbital coverage.

Operational Efficiency Improvements

• 20% more scheduled events through better conflict management, resource coordination, and increased SDA data collection without needing additional assets or personnel.
• 41% reduction in scheduling conflicts through automatic identification and resolution of staffing issues.  
• Communication channels were reduced from six to one centralized system, eliminating missed updates and consolidating scheduling operations.
• Operator workflows improved through built-in PTO tracking, requestor-specific scheduling views, and automated notifications for shifts and certifications.
• Data load reduced by 90%, from 5MB to 500KB, saving roughly 52 hours yearly in calendar-related operations.

Mission Effectiveness Gains

• SDA data collection improved with 20% higher data throughput for operations, boosting threat detection capabilities.
• Scheduling errors dropped from 5-10 per month to zero, supporting reliable space observations.
• Fewer last-minute cancellations and backfills due to improved visibility into staffing needs and availability.

Capability Advancements

• Internal developer confidence levels doubled, based on internal surveys showing stronger onboarding and greater participation in development.
• Production pathway established with cATO allowed the team to deliver secure, regularly updated mission software.
• Daily Site Report (DSR) capability generates structured, auto-populated shift logs and leadership visibility into active operations.
• PTO management consolidation from a separate system into the scheduling app simplifies scheduling processes.
• Improved mission ops and minimized cognitive load on operators through new filtering, status tags, and role-specific tools.

The system has received recognition across the Space Force. During a demonstration, senior leadership described it as having “incredible functionality” and noted that “the chance of mistakes is so much lower” than previous processes. They emphasized the future impact of the system’s data dashboard, which will “show value to everyone of what the government is investing in.”  

Operations staff shared that “changes that happen on-the-fly are now more coordinated and clearly communicated,” highlighting the system’s day-to-day impact on mission execution.

Early demonstrations to other scheduling teams have generated interest in adopting the tool for their operations. Such validation demonstrates the potential for expanding the application across other Space Force units facing similar challenges.

Looking Ahead

The scheduling application has changed how operators carry out their space domain awareness mission. Teams now have the tools for efficient scheduling, effective resource allocation, and continuous operational improvements without waiting for external support.

The Integrated Software Squadron model provides a repeatable structure that other Space Force units can adopt to become self-sufficient software delivery teams. Embedding software capabilities directly into operational units helps fast-track innovation and match mission tools with space security needs.

With upcoming features like interactive dashboards, API integration, and an expanded Daily Site Report system, the app continues to iterate and evolve as a foundational capability. As adoption grows, it remains a model of digitally-enabled SDA operations, protecting U.S. and allied interests in space.

Tech Stack

Frontend

• NextJS (React pages)
• Headless UI (components)
• Tailwind CSS (styling)
  

Backend

• tRPC
• Drizzle
• NodeJS
  

Data Storage

• PostgreSQL
  

Hosting & Infrastructure

• IL4 Platform One instance (production)
• IL2 Platform One (staging)
  

Development Tools

• Figma
• FigJam
• GitLab
• TypeScript
• Confluence
  

Security & Monitoring

• Iron Bank hardened containers
• SonarQube
• GitLab DAST
• FortifyPrometheus
• Grafana

Contract Information

This work began under Rise8’s Autonomy Prime Indefinite Delivery Indefinite Quantity (IDIQ) contract and continued through a follow-up SBIR Specific Topic Award, supporting mission development and digital transformation within the United States Space Force.

Contract period of performance: May 2023 - July 2025