Run the UAG yourself.

The UAG is one container that sits beside Form.io, inside your own environment: from a laptop to an air-gapped data center. Run it with Form.io Enterprise for production, try it on Form.io Open Source, or try it free for 30 days against a trial project on portal.form.io.

PRODUCTION

Enterprise, self-hosted

Form.io Enterprise and the UAG inside your security boundary, with RBAC, revisions, stage deployments and support.

FREE, FULLY SELF-HOSTED

Open Source stack

Form.io Open Source, MongoDB and the UAG in one Docker Compose file, on your own machine or network.

TRY IT

30-day free trial

Start a 30-day free trial project on portal.form.io and run the UAG yourself against it, to try Agentic Formflow and agentic workflows before you deploy.

Get a license

A self-hosted UAG serving a Form.io Enterprise project needs a Form.io license that includes the UAG, in LICENSE_KEY: an online license with UAG servers, or an offline license with the uag option. It is the only license the UAG needs, and covers the Agent API, "Agent: Run task" actions, their engines, the AI Document and the UAG's own database. Ask us for a trial.

Point the UAG at your project

yaml
  formio-uag:
    image: formio/uag
    restart: always
    environment:
      # A container-to-container address: the UAG never needs a public one.
      PROJECT: http://formio-enterprise:3000/yourproject
      PROJECT_KEY: ${PROJECT_KEY}
      LICENSE_KEY: ${LICENSE_KEY}
      # The Form.io server's own secret, so Run task actions can act with an agent role.
      JWT_SECRET: ${JWT_SECRET}
      LOGIN_FORM: https://forms.example.com/yourproject/user/login
      UAG_ENGINES: jev,claude
      TYPESAFE_API_KEY: ${TYPESAFE_API_KEY}
      CLAUDE_API_KEY: ${CLAUDE_API_KEY}

Keep model keys out of the gateway (optional)

Run the engines on formio/uag-engines, or use a local model through Ollama or vLLM so no data leaves your network. Engine setups.

Harden it

Raise PROJECT_TTL, set real secrets, scope roles and permissions, and decide whether remote agents may sign in (MCP_OAUTH). Deployment guide · Security model.

Make a form agent-ready.

You set them in the form builder, without code. The form keeps working for people, with a section an agent fills in.

  1. Tag it uagThe UAG registers only tagged forms, so you decide exactly what agents can see.
  2. Write the criteriaA content component with uag=<task> and uagField=criteria: plain-language instructions, like onboarding a new employee.
  3. Flag the agent fieldsGive each field the agent fills the same uag property, or wrap them in a panel that carries it.
  4. Name the input (optional)Give the free-text field a person types into uagField=input, so @formio/uag-js and agent/extract fill the task from it.
  5. Trigger itFrom a chat over MCP, @formio/uag-js as users type, or an "Agent: Run task" action when a submission is saved through the UAG.
The criteria content component's custom properties: uag set to the task name and uagField set to criteria.
An agent field's custom property uag, set to the task name.

Or ask your coding agent: "Make our claim form agent-ready, with a triage task that decides the claim type from the description." Agentic Coding Plugin

Connect an agent.

There are three ways to connect. Each one authenticates, runs with the caller's permissions and writes only validated data.

Turn on browser sign-in on the UAG with MCP_OAUTH=true and a database (MONGO), then add the UAG to claude_desktop_config.json. The first connection opens your Form.io login, and Claude then acts with that user's roles. The database needs a license that includes the UAG, in LICENSE_KEY.

json
{
  "mcpServers": {
    "formio-uag": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:3200/mcp"]
    }
  }
}

Then ask: "I would like to add a new customer." Full guide, including claude.ai connectors.

Need help going live?

Get a UAG license, architecture guidance and enterprise support for self-hosted deployments.