The ICE STELLA Platform Is Already in Production. The Next Contract to Sustain It Is Still Market Research.

What the ICE STELLA platform RFI asks for, and why October 16 closes the window

ICE’s Office of the Chief Information Officer wants industry to describe how it would sustain the ICE STELLA platform. STELLA is an artificial intelligence environment already in production. The request for information, notice 1d49244e7dbc44fc9ee14f4b22cc9f0d, closes October 16, 2026. ICE says responses feed acquisition planning and requirements development ahead of any procurement. No solicitation exists yet, and ICE discloses no dollar value for the requirement.

Two revenue levers sit here. Which one applies depends on what you hold. If you hold a seat on ICE OCIO’s SWIFT multiple-award contract, your ordering period ends September 14, 2027. This is the current public market research step touching your domain. What gets written in October is the likely basis for whatever evaluation follows. For a firm with no ICE position, the two-week window costs a capability statement and nothing else. It is the one stage where that statement can still change what gets bought.

ICE named five items in scope.

• Sustainment of STELLA, its multi-cloud AI platform, across Google Cloud, Microsoft Azure, and Amazon Web Services.
• A data lakehouse and the pipelines feeding it, plus a Collibra-based data governance environment.
• Application programming interface management and governance, and CORE/TBM operations, ICE’s technology business management reporting.
• Support to ICE’s AI Use Case Inventory and its high-impact AI assessments.
• A planned enterprise “agentic software factory.”

Each item is narrow enough to test against your own past performance in an hour. I would answer one item well rather than claim the full scope.

ICE Put an Enterprise AI Platform Into Production Ahead of the Next Contract to Sustain It

STELLA stands for Secure Technology Environment for Large Language Agents. ICE describes it as production-ready across three commercial clouds, carrying AI applications and an enterprise generative AI chatbot, reportedly live since June 2026. The October notice is market research for the next contract that keeps it running.

DHS still lists ICE’s large language model and retrieval-augmented generation use cases as pre-deployment. Retrieval-augmented generation, or RAG, is where a model answers from an agency’s own documents, not from training data alone.

The AI in government problem here is not capability. A platform in production and use cases recorded as pre-deployment do not line up. That gap is where the sustainment work sits. Operations and maintenance, continuous monitoring, and AI governance support must exist for tools already in use. That work runs today on some instrument, while the next one is still market research. Name your monitoring or governance record first.

SWIFT Is the Plausible Home, and It Stops Taking Orders Before a Follow-On Could Run

ICE OCIO already holds its own multiple-award indefinite-delivery, indefinite-quantity contract for these capability areas. SWIFT, contract 70CTD022D00000014, was signed October 13, 2022. It stops accepting orders September 14, 2027. That one date cuts both ways. SWIFT is the near-term home for a sustainment order, and the wrong home for a follow-on.

The RFI names no acquisition vehicle. I read the SWIFT link as an unconfirmed pattern, not a finding. Other paths stay open: a new ICE OCIO contract, or a DHS-wide vehicle. No specific DHS-wide instrument is identifiable for this scope. ICE could also place a schedule order. USCIS placed one with STELLA JV, LLC, the SWIFT Hyper Automation holder, at a reported $58.6 million ceiling, not obligated spend. USCIS runs its own contracting shop, so that is a path, not a precedent. A blanket purchase agreement is a fourth path, already used for nearby ICE analytics work.

Three steps come before October 16 for a SWIFT holder.

1. Confirm which of the four domains you hold and whether it is set aside for small business.
2. Map your past performance to the capability items ICE named, not your domain label.
3. Write in the layer language ICE described: code generation, assurance, and authorization kept apart. A follow-on organized that way would not inherit today’s domain lines.

The $340 Million Figure Is Not on SWIFT’s Award Record

Two size figures circulate for SWIFT, and only one sits on the award record. That record carries $1.09 billion as total value on the Hyper Automation ordering line, a ceiling, not obligated spend. Whether a modification raised that recorded ceiling, and when, is undisclosed. The $340 million figure in wide circulation is a reported program value from the contract’s establishment, an estimate split across up to eight awardees. It appears on no award record. I would quote neither as the vehicle’s size.

Neither number tells you what work exists. Delivery order 70CTD023FR0000136 was signed April 4, 2025, with performance through March 31, 2028. It carries a $38,217,733.96 order ceiling, not obligated spend, against $92,692.23 in recorded obligation, incremental funding for collaborative services. A separate ICE OCIO award on SWIFT covers robotic process automation and data analytics. It was reported at $36.7 million firm-fixed-price after two offers under a small business set-aside, an award value rather than a confirmed obligation.

• Cite $340 million to leadership and you are quoting a reported figure the award record does not carry.
• Cite $1.09 billion and you are quoting a ceiling on one domain’s ordering line, not the vehicle’s size.
• Neither figure sizes the sustainment requirement, which carries no disclosed value.

Competitive Landscape: Seven Named Holders, Two Doors, and One Name Collision

Seven firms hold the named ICE OCIO positions for these capability areas, across four domains built for up to eight seats. Two of those domains are set aside for small business. None of the seven is named as STELLA’s current sustainment provider.

That is the entry point for a small business DHS prime or subcontractor with no position. A mid-market systems integrator or an AI product firm bidding as prime competes in the two unrestricted domains.

STELLA JV, LLC is reported as a joint venture of Amivero and Steampunk. The name collision with the STELLA platform is a trap in both directions. No award record assigns the joint venture a role on that platform. I would not build a teaming decision on that resemblance.

Adjacent positions matter too:

• Thomson Reuters Special Services holds a separate five-year blanket purchase agreement for ICE Homeland Security Investigations data analytics, at a reported ceiling of up to $125 million, not obligated spend.
• Google Cloud, Microsoft Azure, and Amazon Web Services all carry STELLA, so the hyperscalers and their federal resellers are present without being services competitors.
• Today’s STELLA operations and maintenance provider is undisclosed. The likeliest reason is how ICE describes its orders. Delivery order 70CTD023FR0000136 is recorded as incremental funding for collaborative services and names no system. Sustainment bought that way, or subcontracted under a domain holder, leaves no prime-level entry carrying the platform’s name.

What to Do Before October 16, by What You Hold

The response is a positioning act, not a bid. There is no solicitation to pursue here. A SWIFT holder is defending an ordering period that closes September 14, 2027. What you write in October gets read when and if ICE drafts the requirement. On an IT modernization program this far along, I see no other point of influence.

• SWIFT holder: pull your own order and modification history. Confirm your last order date and each order’s performance end date. Then map past performance to the generation, assurance, and authorization layers, not your current domain line.
• Small business DHS prime or subcontractor without a position: name the single capability on ICE’s list you can evidence. Then open a teaming conversation with a Visualization or Hyper Automation holder before October 16.
• AI product firm or FedRAMP-pursuing SaaS vendor: describe a component that plugs into a control plane the government keeps. FedRAMP is the Federal Risk and Authorization Management Program, the cloud security authorization a software-as-a-service product needs before an agency can run it.
• Systems integrator running enterprise data platforms: lead with past performance on the named tooling. That means the data lakehouse and pipelines, Collibra governance, API management, and CORE/TBM operations.

No group here is pursuing yet. Holders are protecting a closing ordering period, firms without a position are looking for a teaming route, and everyone else is shaping. An RFI built for requirements development, with a fixed October 16 response date, is a shaping window. The priority rises when a solicitation appears, when a vehicle and set-aside get named, or when a value is published. Three things would drop it back to watching: the RFI closing with no follow-on inside two quarters, ICE folding the work into an order you cannot reach, or a sole-source justification naming whoever sustains STELLA today.

FAQ

What is the ICE STELLA platform, and what is ICE asking industry for?

STELLA, or Secure Technology Environment for Large Language Agents, is ICE’s multi-cloud enterprise AI platform. It has run in production since June 2026 across three commercial clouds. The October notice asks how industry would sustain the platform. The scope adds a data lakehouse, Collibra-based data governance, API management, CORE/TBM operations, AI Use Case Inventory support, and a planned agentic software factory.

When are responses due, and what does ICE say it will use them for?

Responses are due October 16, 2026. ICE states the notice supports acquisition planning, requirements development, and evaluation of potential industry capabilities. Market research does not commit ICE to a solicitation or an award.

Is this the SWIFT follow-on, and which contract vehicle would carry the work?

The vehicle is undetermined, because the RFI names none. SWIFT is the most plausible instrument, since it covers these capability areas. That is an unconfirmed pattern, not a finding. Its September 14, 2027 last order date makes it workable for a near-term order, not a multi-year follow-on.

Who already holds ICE OCIO’s platform and automation work, and which domains are set aside?

GovCIO and ICF hold Platforms-as-a-Service, and DevTechnology and Procentrix hold Collaborative Services. Indev and Unissant hold Visualization, and STELLA JV, LLC holds Hyper Automation. Visualization and Hyper Automation are small business set-asides. The other two domains are unrestricted.

Should I respond by October 16, team with a domain holder, or wait for a solicitation?

Respond if you can evidence at least one capability ICE named, since ICE says responses feed requirements development. Team if you are a small business with no position, since the two set-aside domains are the realistic entry. Waiting makes sense only if you have no credible past performance on anything on the list.