About StateSet

Building Autonomous Commerce.

Our mission is to build the operating system for autonomous commerce.

Commerce is a network of commitments. StateSet gives intelligent software the context, authority, coordination, and accountability to carry those commitments through.

Read our mission Join our team

Mission

The work behind every transaction.

A customer pays for a product. A merchant promises delivery. A warehouse reserves inventory. A supplier expects payment. For a business to work, those commitments must become the right actions, in the right sequence, across organizations and systems with different responsibilities.

Software has made each part of that network easier to manage. Businesses can sell through digital storefronts, track inventory across warehouses, accept payments around the world, and communicate with customers instantly. The work of coordinating those capabilities still often falls to people: interpreting requests, checking policies, moving between applications, resolving exceptions, and making sure that what happened in one system is reflected in another.

We believe software should be able to carry much more of this operational work. A business should be able to define an objective, establish the rules, and delegate responsibility for pursuing it. A small team should be able to serve customers and coordinate operations at a scale that once required a much larger organization.

The central challenge

Autonomy has to be reliable.

Commerce commits money, inventory, and obligations. A refund issued twice creates a loss. An order canceled after shipment creates a dispute. An inventory reservation made against unavailable stock creates a promise the business cannot keep. Each action has consequences beyond the conversation that produced it.

An autonomous system must therefore connect flexible reasoning to precise execution. It needs to understand a situation, determine what it is authorized to do, carry work through interruptions, and establish what actually happened. When information is missing or an outcome is uncertain, it must preserve that uncertainty and give someone a clear path to resolve it.

Our thesis is that useful autonomy emerges from bringing these capabilities together. Intelligence supplies the ability to interpret and adapt. The operating system supplies authority, state, coordination, and accountability.

That is the system we are building at StateSet.

A new approach

iCommerce connects intelligence to the work of a business.

We call this approach iCommerce: infrastructure that connects intelligent agents to the operations of a business. StateSet coordinates work across existing commerce systems, combining agent reasoning with policy controls, durable execution, and outcome verification. Alongside the platform, our embedded iCommerce Engine gives developers a commerce runtime they can build directly into applications and agent environments.

What is iCommerce? Embedded iCommerce Engine

Give agents a precise way to act on commerce

An agent needs a structured understanding of the business it is operating. It needs to know which order exists, what has been paid, where inventory is held, and which actions have already occurred. It also needs operations with clear meaning: reserve stock, create an order, authorize a return, issue a refund.

Our embedded engine provides a foundation for these operations in Rust, with commerce state, guarded transitions, transaction handling, and interfaces for applications and AI agents. Developers can run the engine inside their own applications and expose its capabilities through language bindings, APIs, and the Model Context Protocol.

Explore StateSet on GitHub

Make authority and recovery part of execution

A business needs to decide what an agent may do: which records it can access, which operations it can perform, how much it can spend, and when a person must approve the next step. Those boundaries belong in the software that executes the action.

Work also has to survive the conditions of a real business. Providers time out. Events arrive late. A warehouse may respond hours after a request was sent. One part of an operation may succeed while another remains unresolved. StateSet brings together scoped actions, policy enforcement outside the model, durable workflows, and controls for retries and recovery.

See our policy engine

Define success through observable outcomes

Every delegated task needs a clear definition of completion. For an address correction, that might mean the authorized change is confirmed in the relevant systems before fulfillment begins. For a return, authorization, warehouse receipt, and refund settlement are separate milestones.

StateSet connects the original request, relevant commerce records, policy decision, permitted action, and resulting state. This makes it possible to evaluate completed work, identify unresolved cases, and measure the human effort that remains.

Learn about iCommerce

Building the operating system

From a customer request to a verified outcome.

Parts of this vision are already operating in real businesses. StateSet’s published customer deployments include warranty workflows at HydraPak, subscription and support operations at YISE Beauty, and customer service at No Makeup Makeup. These deployments ground the broader architecture in the details of actual commerce work.

Consider an ordinary warranty request. A customer reports that a product has failed. Resolving the request may require identifying the product, finding the purchase, interpreting the warranty policy, checking replacement inventory, obtaining approval, creating a replacement order, and following its progress through fulfillment.

From the customer’s perspective, this is one problem. Inside the business, it crosses several systems and responsibilities. The operating system has to maintain continuity across the whole process, including the periods when it is waiting for information, an external event, or a person.

Understand the request

Identify the product, find the purchase, and bring the customer and commerce context into one workflow.

Apply the rules

Interpret the warranty policy, check eligibility, and determine which actions are authorized.

Coordinate the work

Check replacement inventory, obtain approval when needed, and create the replacement order.

Verify the outcome

Follow fulfillment, preserve unresolved states, and give an operator a clear path when judgment is required.

This is where the engineering becomes demanding. The system must handle changing policies, concurrent requests, partial failures, software upgrades, and records that disagree. It must distinguish an action that failed from one whose outcome is still unknown. It must help an operator understand what has happened and what remains to be done.

Much of this work is practical systems engineering: databases, permissions, workflow execution, integrations, testing, observability, and product design. Applied AI is part of the machine, and its usefulness depends on how well the surrounding parts work together.

We see a concrete path forward. Start with a meaningful workflow. Define the conditions under which the system may act. Specify the evidence required for completion. Test the cases that should succeed, the cases that should be denied, and the cases that require help. Operate the workflow, learn from the exceptions, and use those lessons to support a broader range of work.

Greater autonomy requires a more complete account of authority, dependencies, and outcomes. Our ambition grows with our ability to make those responsibilities explicit and dependable.

What comes next

A foundation for commerce between software agents.

Over time, we believe this foundation can also support commerce between software agents. An agent acting for a buyer could request a quote, commit a budget, place an order, and track fulfillment. An agent acting for a supplier could confirm availability, accept the commitment, and coordinate delivery. Payments and settlement would need to remain connected to the authority under which each commitment was made.

That future requires a common way for software to represent commercial intent, commit resources within defined limits, and establish what each party has done. We intend for StateSet to help provide that foundation.

The larger goal is to change what a small business team can accomplish. Founders should be able to spend more of their attention on products and customers. Operators should be able to supervise broader responsibilities with a clear view of the work. Developers should be able to build new commerce experiences on infrastructure that already understands the operations beneath them.

We want the reach of a business to depend increasingly on the quality of its ideas and execution, with software carrying more of the coordination required to bring them into the world.

Join our team

Build the system that carries real responsibility.

Building StateSet brings together systems engineering, applied AI, commerce operations, payments, security, and product design. These disciplines are closely connected. How we represent an order shapes what an agent can do. How we handle a payment affects how a workflow recovers. How we present an exception determines whether a person can resolve it quickly and confidently.

We believe a small, focused team can make substantial progress by understanding these connections and taking responsibility for the whole system. The work rewards people who can move between a difficult technical problem and the business operation it serves, and who care about what happens after software reaches a customer.

Systems thinking

How we represent an order shapes what an agent can do. How we handle a payment affects how a workflow recovers. We care about the connections between disciplines.

Whole-system ownership

We move between difficult technical problems and the business operations they serve, and we care about what happens after software reaches a customer.

Energy, effort, and execution

We bring curiosity, discipline, and follow-through to the details of real commerce work. We follow problems from first principles into messy operating conditions.

Our goal is to give software the ability to carry real operational responsibility—and give businesses the confidence to delegate it.

That is what we mean by building autonomous commerce.

View open positions Contact us