--- title: StateForge: GPU-Native Persistent-State Engine | SpinForge url: https://spin-forge.com/stateforge description: A GPU-native persistent-state engine connecting supported live-data, computation, indexing, transaction and persistence workflows. --- AI INFRASTRUCTURE / GPU-NATIVE PERSISTENT STATE [The full offering](https://spin-forge.com/platform) # StateForge. A GPU-native persistent-state engine connecting supported live-data, computation, indexing, transaction and persistence workflows. [Discuss StateForge](https://spin-forge.com/contact?product=stateforge) Customer outcome [Operate compute and data workflows](https://spin-forge.com/platform/compute-data-operations) Available now CLI MCP Headless Choose your access mode THE PRODUCT, IN PRACTICE ## Keep useful state close to the work. When GPU applications repeatedly exchange live state with separate data systems, the data path becomes part of the engineering problem. StateForge brings live and stored state into a GPU-centered workflow, including supported indexing, transactions and persistence. The purchase is a defined state capability and integration—not a blanket promise to replace every database, queue and analytics system. BUILT FOR GPU-data infrastructure, streaming-system and stateful-application teams evaluating a bounded state subsystem. CHALLENGES PRODUCT RESPONSE ## The problem you face. What StateForge changes. 01 ### State is separated from GPU computation The application needs data to compute, while the systems that hold that data may follow a different operating path. StateForge brings supported live state and processing into a GPU-centered workflow, targeting the repeated handoffs in the selected workload. 02 ### Several data responsibilities become integration work Indexing, transactions and persistence can each create another boundary for the application team to manage. The engine connects those responsibilities within the supported state workflow. Compatibility and semantics are defined for the portion of the stack being integrated. 03 ### Consolidation is too broad a first purchase Replacing an entire data stack at once makes it hard to specify what must keep working. A StateForge engagement can define one state subsystem, its required data operations and its persistence/recovery contract before any broader replacement is considered. WHAT YOU GET ## A defined capability. A useful output. The product scope below describes the capability and outputs to confirm for your release. Custom integration, operated delivery and additional engineering are separately agreed. 01 ### A persistent-state capability The selected live/stored-data functions within the GPU-native engine scope. 02 ### Supported data operations The indexing and transaction responsibilities agreed for the application. 03 ### A persistence boundary The qualified connection between runtime state and the retained storage path. 04 ### A defined integration Explicit compatibility, data ownership and operating responsibilities for the selected subsystem. AVAILABLE NOW ## One product. Three ways to work. StateForge is fully available with CLI, MCP and headless access. Use the interface that fits your terminal, your agents or your automated workflow. 01 / CLI ### For your terminal. Run the product from a terminal or script, alongside the tools your team already uses. [Get CLI access](https://spin-forge.com/contact?product=stateforge&interface=cli&brief=I+would+like+StateForge+access+through+CLI.+Please+share+the+setup+documentation+and+configuration+for+the+selected+product.+We+will+confirm+the+environment%2C+license+scope+and+workflow+during+onboarding.) 02 / MCP ### For your agents. Connect MCP-compatible clients and agents to the product’s exposed capabilities. [Get MCP access](https://spin-forge.com/contact?product=stateforge&interface=mcp&brief=I+would+like+StateForge+access+through+MCP.+Please+share+the+setup+documentation+and+configuration+for+the+selected+product.+We+will+confirm+the+environment%2C+license+scope+and+workflow+during+onboarding.) 03 / HEADLESS ### For your workflows. Operate without a graphical interface in unattended, scheduled or pipeline-driven work. [Set up headless access](https://spin-forge.com/contact?product=stateforge&interface=headless&brief=I+would+like+StateForge+access+through+headless.+Please+share+the+setup+documentation+and+configuration+for+the+selected+product.+We+will+confirm+the+environment%2C+license+scope+and+workflow+during+onboarding.) Product-specific inputs, hardware requirements and result guarantees still apply. An access mode does not change your license or deployment scope. [Explore all product interfaces](https://spin-forge.com/developers?section=access-directory) EXAMPLE CUSTOMER WORKFLOW ## Evaluate one GPU-resident state subsystem A stateful GPU application needs a more coherent path between live computation and retained state. Illustrative use of the supported scope, not a customer case study or a measured result. 1. 01 Identify one subsystem and its data, consistency and recovery requirements. 2. 02 Integrate the qualified StateForge capabilities with that workload. 3. 03 Evaluate correctness, data movement and recovery before extending the scope. THE OPERATING PATH ## Follow the work. Know the boundary. A product workflow illustration, not a live execution or deployment test. Choose a stage to explore its role. 01 / Ingest Accept data into the agreed network-to-GPU path. IN YOUR WORKFLOW ## Start with your task. Agree the useful outcome. GPU-data infrastructure, streaming-system and stateful-application teams evaluating a bounded state subsystem. What you bring The state workload, data size, access patterns, required transaction/consistency behavior and persistence environment. What a useful evaluation measures - Correctness of the agreed state operations - Data-path overhead for the representative workload - Persistence and recovery behavior at the accepted scope Where it fits Use the selected product in a qualified customer environment, or agree a defined implementation with SpinForge. A hosted or managed service is quoted for its actual operating responsibilities; it is not automatically included with software access. QUESTIONS BEFORE YOU BUY ## A clear scope. No hidden assumptions. **How can we use StateForge?**CLI, MCP and headless access are all available. Run from a terminal or script, connect an MCP-compatible client, or use the product without a graphical interface. Choose the mode during onboarding and receive its setup instructions. Runtime requirements and supported operations remain product-specific. **What is the important product boundary? **The supplied description establishes the architecture and consolidation aim, not universal compatibility with the systems it might replace. Durability, recovery, isolation and performance must be established for the delivered deployment. Managed operation is a separate contracted responsibility. **What comes with the selected license? **The agreed StateForge release, its supported interfaces and outputs, the applicable checks and the support stated in your order. The plan defines users, workflow, environment and capacity. Source-code transfer, unrestricted redistribution and bespoke engineering are not automatically included. **Can SpinForge implement or operate it for us? **Request a scoped engineering or operated-service proposal. It identifies what our team delivers, where the workload runs, infrastructure costs, acceptance requirements and ongoing support. Your software subscription alone does not activate a hosted runtime. [Explore engineering](https://spin-forge.com/engineering) **How do we establish fit before production? **Agree the model or workload, current baseline, environment, required output and acceptance tests. Evaluate the selected release against those conditions. A product description or a test count does not establish a gain on a different customer workload. [Plan an integration](https://spin-forge.com/integration) SOFTWARE / OPERATED DELIVERY By proposal Customer-hosted access and a service operated by SpinForge are different scopes. Confirm the release, deployment and included support before activation. [Plans & delivery](https://spin-forge.com/pricing) PUT STATEFORGE TO WORK ## Tell us what needs to improve. Bring a representative workload and the result your team needs. We’ll define the product, deployment and engineering scope around that task. [Discuss this workflow](https://spin-forge.com/contact?product=stateforge&brief=Product%3A+StateForge%0AOur+challenge%3A+State+is+separated+from+GPU+computation%0AWorkload+%2F+baseline%3A+%0AEnvironment%3A+%0ARequired+output%3A+%0AAcceptance+measures%3A+Correctness+of+the+agreed+state+operations%3B+Data-path+overhead+for+the+representative+workload%3B+Persistence+and+recovery+behavior+at+the+accepted+scope%0ADelivery+preference+%28software+%2F+engineering+%2F+managed%29%3A+) **Related products, workflows and system connections + **RELATED CAPABILITIES ## Connect the right products. Distinct responsibilities. Explore each scope before choosing a combined deployment. [### AgentForge An operating layer for generating, scheduling, validating, storing and replaying agentic-AI workloads across CPU/GPU infrastructure.](https://spin-forge.com/agentforge) [### GridForge AI compute-fabric planning software that maps workloads against power, cooling, memory, network and silicon resources.](https://spin-forge.com/gridforge) [### AI infrastructure Four AI-infrastructure products: StateForge, KX MemoryForge, GridForge and AgentForge.](https://spin-forge.com/infrastructure) ONE PLATFORM / OR A DIRECT PURCHASE ## Compute & Data Operations with StateForge. Activate this capability inside a qualified compute & data operations workflow. Compatible methods and required shared checking are included once within that workflow; the product remains independently purchasable. Capacity, release, environment, result contract and operating responsibilities are specified before activation. Choosing an additional method is not permission to add an unrelated workload or unqualified deployment. [Explore Compute & Data Operations](https://spin-forge.com/platform/compute-data-operations) [Choose workflow capacity](https://spin-forge.com/plans?configuration=compute-data-operations&product=stateforge) CONNECTED WORKFLOWS ## Use StateForge in your workflow. The product remains independently available. These customer-specific solution paths use the relevant supported capabilities, with integration and delivery rights agreed separately. [07 ### Cloud & infrastructure enablement Build a supported optimization, inference-performance or agent-workload offering on your infrastructure, with a clear product boundary and operating model.](https://spin-forge.com/solutions/cloud-provider-services) [09 ### Private computational deployments Use the appropriate SpinForge capability in a supported customer-controlled environment. Choose CPU execution where the product supports it and acceleration where the workload justifies it.](https://spin-forge.com/solutions/private-computation) [Explore all 17 solution workflows](https://spin-forge.com/workflows) FROM PRODUCT TO CUSTOMER WORKFLOW ## A useful outcome. A defined delivery. Commission the model, integration and acceptance work needed for your task. Existing products stay independently available. [02 / Scoped customer program ### Maintain a recurring decision Commission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.](https://spin-forge.com/programs/living-decisions) [03 / Scoped customer program ### Improve a computational workflow Commission a bounded performance improvement with source identity, numerical acceptance and the appropriate checking evidence.](https://spin-forge.com/programs/compute-improvement) [Explore decision programs](https://spin-forge.com/decision-systems) THE WHOLE-SYSTEM ROLE ## StateForge in a wider workflow. Persist typed computational artifacts, source revisions, reuse conditions and replay records close to appropriate workloads. POTENTIAL SYSTEM CONTRIBUTION Artifact schema, tenant isolation and actual durability guarantees must be qualified; not every metadata operation needs a GPU. [S1 · Joint workload & machine optimization](https://spin-forge.com/system-synergies/joint-configuration) [S3 · Checked computational memory](https://spin-forge.com/system-synergies/checked-computational-memory) [S6 · Checked improvement feedback](https://spin-forge.com/system-synergies/checked-improvement) [See this product in the map](https://spin-forge.com/system-synergies/product-map?q=StateForge) [Define an integration evaluation](https://spin-forge.com/system-synergies/evaluation) The product is independently available through CLI, MCP and headless access. The joins above are integration candidates; compatibility, authority, data rights and end-to-end benefit must be established for the selected workflow. START WITH THIS PRODUCT Use the software directly or ask us to scope the implementation. [Software access](https://spin-forge.com/plans?product=stateforge) [Have us do the work](https://spin-forge.com/contact?product=stateforge&delivery=engineering)