Developers

Build operational software—not just applications

AI-first platform for operational WebApps, workflows, and autonomous agents.
Connect business systems.
Coordinate people and AI.
Build secure operational software on one controlled account.

Build on the operational layer that runs work between your systems, people, and AI—not another app beside your stack.

curl — start workflow

curl -X POST https://acme-ops.tealfabric.io/api/v1/processes/vendor_intake/execute \
  -H "X-API-Key: $TF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vendor_name":"Acme Parts","tax_id":"FI-12345"}'

Documentation OpenAPI Processflow skeleton Sign in Full platform guide

Examples

What customers build

Developers ship operational software on Tealfabric—not generic CRUD apps beside the stack.

Customer onboarding
Order orchestration
Field service coordination
Partner and vendor onboarding
AI approval workflows
Claims processing
Contract approvals
Customer provisioning
Support escalation
Renewal automation

Solution delivery flow

Build → deploy → CDN → APIs → operate

01 Build02 Deploy03 CDN04 APIs05 Ops

Local dev · partner-portal-next/

AI-assisted build

Cursor + Claude scaffold Next.js app

Lovable prototype → export to repo

app/page.tsx · intake form component

lib/tealfabric-client.ts · OpenAPI types

POST /api/v1/webapps/... (server route only)

Simulated flow — AI-assisted Next.js app published to the platform; users on CDN WebApp; logic through controlled APIs

Build → deploy → CDN → APIs → operate — see developer platform for all eight API surfaces.

Quickstart

Your first workflow in 5 minutes

Sandbox, scoped key, one workflow, one execute call—no sales call required.

Picture the path before you read the full guide: obtain credentials, wire a workflow, connect one system, execute, and inspect the run history.

Sign in at tealfabric.io and provision a sandbox account.
Create a scoped API key—server-side only, one per solution or environment.
Start from the Processflow skeleton or import a workflow template.
Connect one system (or use the built-in test connection).
POST to /api/v1/processes/{name}/execute, then open the run in Operations.

curl — start workflow

curl -X POST https://acme-ops.tealfabric.io/api/v1/processes/vendor_intake/execute \
  -H "X-API-Key: $TF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vendor_name":"Acme Parts","tax_id":"FI-12345"}'

Start here

Sandbox account and OpenAPI

Automate workflows, call connections, publish WebApps, and extend AI with team playbooks—all on one account with reviewable history. Target the documented contract at /api/docs, not reverse-engineering the UI.

tealfabric.io OpenAPI explorer

API

REST API and scoped keys

/api/v1/ for workflows, connections, Datapools, WebApps, and logs—API key server-side only.

External schedulers start workflows; step code uses the built-in API client. Keys stay in servers and CI, never in browser JavaScript.

curl — start workflow

curl -X POST https://acme-ops.tealfabric.io/api/v1/processes/vendor_intake/execute \
  -H "X-API-Key: $TF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vendor_name":"Acme Parts","tax_id":"FI-12345"}'

API reference Governance →

Ship

Build, publish, and operate

AI-assisted portals, WebApp versions, CDN, skills folders—each with its own go-live path.

Scaffold with Cursor or Claude, publish via developer tools and the WebApps API. When nightly sync or partner portals fail, trace execution in the operations console—no separate monitoring stack for typical workloads.

Processflow skeleton Cursor tools Claude tools Lovable tools WebApps →Operations →

Skills playbooks

Versioned AI playbook folders your team publishes—what agents can read, which connections they may call, and when human approval is required.

Skills are tenant-owned playbooks loaded on demand—not generic automation snippets or shadow agents. Author folders that define context, allowed tools, and human-in-the-loop gates before execute_tenant_integration runs.

AI and agents →Human approval workflow →

Pilot

Partner checklist

One production workflow, one playbook pack, safety rules—not login alone.

Sandbox account, top connections, ProcessFlow template, skills playbooks, tool safety config, scoped API keys, operations alerts.

Security pack →Start a pilot →Full platform guide →

Essentials

Patterns, stack, and what you build on

Nightly sync you own

Your scheduler starts a workflow → connections run → Datapool updated → alerts on failure.

Partner portal

WebApp content in CI → publish on Tealfabric → your domain → workflow validates and writes to Datapool.

In-workflow enrichment

TypeScript step calls connections and Datapools via the built-in API client—no middleware server.

Support AI with your playbook

Deploy skills playbooks → Trace AI follows your rules → only platform-allowed tools run.

Contract-first partner API

Validate in the API explorer → implement in your service → scoped staging key → promote after CI checks.

Platform capabilities you build on

ProcessFlowIntegrationsDatapoolsWebAppsDocuments and CDNOperationsTrace AI

TypeScript / JavaScript

Node services, Next.js portals, workflow step code, serverless, CI pipelines

Python, Go, Java

ETL, microservices, partner gateways

Cursor, Claude, Lovable

AI-assisted scaffolding—publish via API and developer tools

Shell / curl

CI smoke tests and scheduled triggers

AI coding tool plugins

Cursor tools

Claude tools

Lovable tools

Full capability breakdown on Developer platform and APIs →

Ship on Tealfabric

Ready to build your first controlled workflow?

Provision a sandbox, wire your top connections, and ship one production workflow with scoped API keys—then add team playbooks when AI joins the loop.

Developer platform · Security pack · Compare approaches