Platform · Agent runtime

The warden of your data and your agents.

The name is literal: infrastructure for AI needs guardrails, and Ward is the warden that holds them. Most teams that want agents on their data stop at the security review. The problem is never the model. It is that nobody can say what the agent is allowed to read, what it did last Tuesday, or what happens when it is wrong. Ward makes those three things answerable before you write the first agent.

Request access Read the docs

What it guarantees

A governed runtime for building agentic logic against your own data, with every action scoped and logged.

Declare the tables an agent can see. It cannot reach past them.

Ward AI drafts the agent definition and its permission scope from a plain-English brief. You approve the scope before it runs.

Read-only by default. Write actions require an explicit grant and leave a record.

Every query, tool call and result is logged with the agent identity that made it.

Model-agnostic. Bring Claude, GPT, Gemini or a model in your own VPC.

In the console

What this looks like when you actually use it.

Scope is declared, not prompted

An agent reaches the sources on its list and nothing else. Not the ones it can name, not the ones it can guess, not the ones a clever instruction talks it into. Scope is enforced when the query runs, below the model, so prompt injection cannot widen it.

Ward AI drafts, you approve

Describe the job in plain English and Ward AI proposes the agent and the permissions it would need. The proposal sits there until a human approves it. Nothing runs on a draft.

app.getward.ai

A Cedar policy open in Ward’s editor, permitting the viewer role to query the sales.store_sales_daily model when the region is WE, with unit_cost, margin and extended fields marked hidden. — **Policy editor.** Row scope and hidden fields in five lines, with autocomplete over your own models and errors underlined as you type.

Ward’s Policies list for the Acme tenant: eight Cedar policies, seven permitting and one forbidding, each with an inline edit control. — **Policies.** Access is eight Cedar policies you can read in a sitting, not a permissions matrix nobody opens.

Ward’s access log: every authorization decision recorded for the tenant, timestamped to the second in UTC, with outcome, action, resource, actor, and the milliseconds each decision took. — **Access log.** Every authorization decision, allowed or denied, with the actor and the latency. This is the page the security review asks for.

Ward’s Providers page: OpenAI, Anthropic, Google, Azure OpenAI, Groq, OpenRouter, xAI, Mistral and Ollama, each showing how many models it exposes and whether it has been configured. — **Providers.** Nine providers, your keys. On this tenant only Ollama is configured, running local.

Ward’s Model Profiles table: four provider-and-model pairs that agents, chats and dashboards route through, including Qwen 3.8 on llama.cpp, DeepSeek v4 Flash, and GLM 5.3 marked as the default. — **Model profiles.** One table decides which model answers. Change the default and every agent follows it.

Full running agents guide →

The rest of the platform

Five more primitives. Adopt them in any order.

Warehouse

Live in hours, not weeks.

A running warehouse built from the systems you already have, without a migration window.

Connectors

540 sources. Read-only by default.

Managed ingestion from warehouses, lakes, SaaS APIs, databases and flat files.

Semantic layer

One definition of revenue. Enforced.

Metrics, dimensions and grain defined once and enforced everywhere, including in what agents are allowed to compute.

Query and chat

Ask in English. Read the SQL.

Natural language over the semantic layer, with the generated SQL always visible.

Governance

The answers your security review needs.

Row-level policy, scoped credentials, and an audit log that covers humans and agents equally.

Start with one source.

Deploying is free. The whole console, every connector, and nothing to license.

Get a demo → Take the 3-minute assessment

Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly

Get started

Find out what your data has been hiding.

Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.

Step 1 of 3

What are your goals?

Reduce stockouts Cut shrinkage Optimize pricing Improve demand forecasting Better promo ROI Understand customer behavior

Step 2 of 3

About your operation

Retail vertical

Number of stores

Step 3 of 3

Your contact info

Full name

Work email

Company

Phone (optional)