Skip to content

Open Source

Open Foundation. Open Standard.

Intended open sources two projects. IntendedOps is the governed back-office operating system — a complete deployable SaaS back-office where AI agents run operations under governed trust tiers. The Open Intent Layer is the canonical taxonomy for describing what agent actions are intended to do. Both are Apache 2.0 and work independently of the commercial Intended platform.

Two open source projects

Clone either one today. Both Apache 2.0. Both production ready.

Product · Apache-2.0

IntendedOps

Governed back-office operating system for SaaS

A complete back-office where AI agents run operations under governed trust tiers. Policy engine, audit ledger, approval workflows, and dozens of adapters for databases, auth, payments, email, and more — all in one monorepo. Native governance is built in and works offline.

Standard · Apache-2.0

Open Intent Layer

Canonical taxonomy for AI agent actions

The open standard for describing what agent actions are intended to do. 14 enterprise domains, 80 categories, stable OIL-identifiers. Vendor-neutral, extensible, and designed to be cited in compliance frameworks and enterprise capability maps.

These are the only two projects Intended open sources. The Intended platform itself — Large Intent Models, Enterprise Capability Engine, cryptographic Authority Tokens, compliance crosswalks, and the SDK components that connect to it — is commercial and available to platform customers.

IntendedOps quickstart

Zero to governed operations in five minutes.

Clone the monorepo, drop in a minimal config, and run. Native governance handles the full intent → policy → approval → execution → audit loop locally, with no external services required.

bash
git clone https://github.com/intended-so/intendedops.git
cd intendedops
pnpm install

# Minimal config — SQLite, native governance, no external dependencies.
cat > intendedops.config.ts <<'EOF'
import { defineConfig } from '@intendedops/config';

export default defineConfig({
  name: 'My SaaS',
  database: { provider: 'sqlite' },
  auth: { provider: 'builtin' },
  governance: { provider: 'native' },
});
EOF

pnpm build && pnpm start
Clone, configure, run. Native governance enabled by default.

What you get in the monorepo

One repository. Four layers.

Governance

Trust tiers, policy engine, native decision runtime, audit ledger, approval workflows, fail-closed enforcement.

Back-office domains

Billing, subscriptions, support, sales, contracts, vendors, identity, compliance — each with a governed agent.

Infrastructure adapters

Database (SQLite, Postgres), auth (JWT, OAuth), AI (Anthropic, OpenAI), payments (Stripe, PayPal), storage, email, queue, cache, notifications.

Operator console

Next.js dashboard for approvals, audit review, policy authoring, and operator workflows — shipped in-repo.

Upgrade path

One config line from native to the Intended platform.

Native governance in IntendedOps is designed for startups and small teams. When you need enterprise-grade intent verification — Open Intent Layer classification, Enterprise Capability Engine mapping, cryptographic Authority Tokens, compliance framework crosswalks, and independently verifiable audit evidence — point the same governance contract at the Intended platform. No code changes.

typescript
// Upgrade from native governance to the Intended platform.
// One config field. No code changes. No migration.

import { defineConfig } from '@intendedops/config';

export default defineConfig({
  name: 'My SaaS',
  database: { provider: 'postgres', url: process.env.DATABASE_URL },
  governance: {
    provider: 'intended',
    apiKey: process.env.INTENDED_API_KEY,
  },
});
The upgrade is a single config field. Everything else stays the same.

What native governance covers. What the Intended platform adds.

CapabilityIntendedOps nativeIntended platform
Trust tiers (T0–T4)YesYes
Policy engineYesYes, plus Open Intent Layer classification
Audit trailIn-memory or databaseHash-chained, immutable, externally verifiable
Intent classificationLarge Intent Model + canonical taxonomy
Capability mappingEnterprise Capability Engine
Authority tokensRS256, 300s TTL, single-use nonce
Compliance crosswalksSOC 2, NIST AI RMF, EU AI Act
Evidence exportIndependently verifiable bundles

Start with the open foundation

Deploy IntendedOps. Adopt the Open Intent Layer. Upgrade to the platform when enterprise verification matters.

Both open source projects stay Apache 2.0 forever. The Intended platform is the commercial layer — Large Intent Models, Enterprise Capability Engine, Authority Tokens, evidence export, and full SDK support in TypeScript, Python, and Go. Platform SDKs are distributed to customers through platform access.