Developers
API-first: compose ProcessFlow, WebApps, integrations, and tenant skills on one tenant—inside the platform boundary, not beside it.
Solution delivery flow
Build → MCP deploy → CDN → APIs → operate
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)
Build → deploy → CDN → APIs → operate — see developer platform for all eight API surfaces.
Start here
Sign in, provision a sandbox, discover contracts before you write code.
Automate processes, call integrations, publish WebApps, and extend agents with tenant skills—all on one tenant with audit trails. Target the documented contract at /api-docs/, not reverse-engineering the UI.
API
/api/v1/ for processes, integrations, DataPool, WebApps, and logs—X-API-Key server-side only.
External schedulers call execute-process; step code uses the injected api client. Keys stay in servers and CI, never in browser JavaScript.
curl -X POST https://your-tenant.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"}'Ship
AI-assisted portals, WebApp versions, CDN, SKILLS/—each with its own go-live path.
Scaffold with Cursor or Claude, publish via MCP and WebApps API. When nightly sync or partner portals fail, trace execution in Monitor—no separate APM stack for typical workloads.
Agents
Tenant skills via load_tenant_skill—with MCP guardrails and human approval.
Author SKILLS/ for when to load context, which integrations may run, and what needs request_human_input before execute_tenant_integration.
Pilot
One production workflow, one skill pack, guardrails—not login alone.
Sandbox tenant, top integrations, ProcessFlow template, SKILLS/, MCP guardrails, scoped API keys, Monitor alerts.
Essentials
Nightly sync you own
Your scheduler calls execute-process → integrations run → DataPool updated → Monitor alerts on failure.
Partner portal
WebApp content in CI → publish on Tealfabric → custom domain → process validates and writes DataPool.
In-process enrichment
TypeScript step calls integrations.execute and datapool via built-in api client—no middleware VM.
Support agent with your playbook
Deploy SKILLS/triage/ → Trace AI follows your rules → only platform-allowed tools run.
Contract-first partner API
Validate in Swagger → implement in your service → scoped staging key → promote after CI curl checks.
Platform capabilities you compose
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
Full capability breakdown on Developer platform and APIs →
Ship on Tealfabric
Provision a sandbox, wire your top integrations, and ship one production process with scoped API keys—then add tenant skills when agents join the loop.
