Tealfabric

Solution delivery flow

Build → MCP 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 via MCP; users on CDN WebApp; logic through governed APIs

Build on Tealfabric

“Your language, our contract—compose ProcessFlow, WebApps, and integrations without rebuilding the platform underneath.”

Platform

Developer platform and APIs — your solution workplace

Extend Tealfabric into customer solutions with REST APIs, OpenAPI, scoped keys, MCP tools, and AI-assisted workflows—using Cursor, Claude, or Lovable to ship faster, then publish to your tenant with full audit and governance.

API documentationPartner patterns

Your team extends Tealfabric into customer solutions—using automation, data, integrations, and apps the platform already provides.

Teams that adopt a platform still often build parallel stacks: custom API gateways, separate portal hosting, glue scripts that bypass governance, and AI experiments disconnected from real integrations and data.

Tealfabric is designed so your solutions stay inside the platform boundary. Use HTTP APIs, the API explorer, and scoped API keys—the same surfaces the product UI uses—to wire portals, backends, CI pipelines, and AI-assisted tooling into governed capabilities.

  • Build customer solutions on the platform—not beside it or inside its core codebase
  • HTTP + JSON from any stack; OpenAPI at /api-docs/ for contract-first development
  • Scoped API keys per solution and environment—server-side only
  • AI-assisted workflows with Cursor, Claude, and Lovable—ship via MCP and WebApps API
  • Publish WebApps, CDN assets, public docs, and tenant skills with deliberate release models
  • ProcessFlow API plus built-in api helper inside step code
  • Trace AI, tenant skills, and MCP tools within deployment guardrails
  • Monitor and logs for everything your team deploys to the tenant

OpenAPI explorer at /api-docs/

Solution patterns

Typical ways customer teams deliver on the platform.

  1. cron → execute
    process API

    Nightly sync you own

    Your scheduler calls execute-process → integrations run → DataPool updated → Monitor alerts on failure.

  2. CI publish
    custom domain

    Partner portal

    WebApp content in CI → publish on Tealfabric → custom domain → process validates and writes DataPool.

  3. api client
    in step code

    In-process enrichment

    TypeScript step calls integrations.execute and datapool via built-in api client—no middleware VM.

  4. SKILLS/
    Trace AI

    Support agent with your playbook

    Deploy SKILLS/triage/ → Trace AI follows your rules → only platform-allowed tools run.

  5. Swagger
    scoped key

    Contract-first partner API

    Validate in Swagger → implement in your service → scoped staging key → promote after CI curl checks.

End-to-end flow

Build with AI tools, publish via MCP, serve on CDN—logic through APIs.

A developer scaffolds a Next.js partner portal with Cursor and Claude, exports a Lovable prototype into the repo, and deploys through MCP and the WebApps API. End users load the app on a custom domain with CDN assets; form submissions hit server-side routes that call ProcessFlow and integrations—never exposing API keys in the browser.

Solution delivery flow

Build → MCP 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 via MCP; users on CDN WebApp; logic through governed APIs

Capabilities

One tenant, your solutions—automate inside and outside the platform.

No required vendor SDK—your HTTP clients are fine. Use OpenAPI for codegen if you want contract-first development.

  1. compose
    don’t fork core

    Compose, don’t rebuild

    Extend ProcessFlow, WebApps, DataPool, and integrations—not the platform core.

    Your team delivers customer solutions on top of Tealfabric: same tenant, same audit trails, same integrations and processes—exposed through documented APIs and clear publish models.

  2. /api/v1/*
    HTTP + JSON

    REST API — your main surface

    /api/v1/ for processes, integrations, DataPool, WebApps, documents, and logs.

    Run processes and check queue status, execute integrations, manage entities and documents, create and publish WebApps, and read operational analytics—with consistent success + data response shapes.

  3. /api-docs/
    Swagger

    OpenAPI / API explorer

    Discover contracts at /api-docs/ before you implement in your repo.

    Inspect payloads, test calls with your API key, and target the documented contract—not reverse-engineering the UI. Contract-first partner integrations start in Swagger.

  4. X-API-Key
    scoped · rotate

    Scoped API keys

    Per-solution identity with scopes, expiry, rotation, and rate limits.

    X-API-Key on server-side requests—processflow.execute, integrations.execute, entities.read, and more. One key per solution or environment; rotate without breaking unrelated workloads. Keys stay in servers and CI, never in browser JavaScript.

  5. Cursor · Claude
    Lovable · MCP

    AI-assisted solution development

    Build faster with Cursor, Claude, Lovable—and ship on governed platform APIs.

    Use modern AI coding tools to scaffold Next.js portals, generate API clients from OpenAPI, and iterate WebApp content—then publish to your tenant via MCP tools and WebApps API. Trace AI, tenant skills, and MCP connect agents to real integrations and data.

  6. execute-process
    api in steps

    ProcessFlow API & built-in client

    Execute, queue, and chain platform capabilities from outside and inside steps.

    External schedulers call execute-process; step code uses the injected api / $api client with tenant and execution context applied automatically—no hand-maintained auth headers in every step.

  7. WebApp vN
    CDN · SKILLS/

    Publication models that match reality

    WebApp versions, CDN assets, public docs, skills—each with its own go-live path.

    CI pushes WebApp content → publish version N → smoke test live URL. CDN for static assets; public docs for governed downloads; SKILLS/ folders for agent playbooks without redeploying the platform.

  8. Monitor
    queue · logs

    Operate what you ship

    Monitor, queues, logs, and analytics for your tenant’s workloads.

    When your nightly sync or partner portal fails, trace WebApp execution logs, linked process runs, and integration queue status in the same console—no separate APM stack required.

Languages and AI tooling

TypeScript / JavaScript

Node services, Next.js portals, serverless, CI pipelines

PHP

Enterprise integrations and ProcessFlow step code

Python, Go, Java

ETL, microservices, partner gateways

Cursor, Claude, Lovable

AI-assisted scaffolding—publish via API and MCP

Shell / curl

CI smoke tests and scheduled triggers

Platform capabilities you compose

ProcessFlow

Business rules, orchestration, file handling, OCR, LLM steps

Integrations

CRM, ERP, email, files, HTTP, databases

DataPool

Structured storage and queries for workflows and apps

WebApps

User-facing UI bound to your processes

Documents & CDN

Files, reviews, public static delivery

Monitor

Queues, logs, and failures for what you deployed

Trace AI & MCP

Governed agents with tenant skills and platform tools

Fits the platform

External callers hit WebApp URLs, webhooks, and CDN links. Your backends orchestrate what happens behind them with /api/v1/. ProcessFlow steps chain capabilities with the built-in api client. Agents use Trace AI, tenant skills, and MCP within guardrails.

WebApps Process Automation AI, Agents, and MCP Platform Ops and Observability

Deliver real solutions on a governed platform

See APIs, MCP, WebApp publish, and AI-assisted development in your tenant.

We walk through OpenAPI discovery, scoped keys, CI publish pipelines, Cursor-to-MCP workflows, and Monitor for what your team ships.

Book a demoDocumentationFor developers