InsightStudio — the SaaS marketplace

InsightStudio is the browser-based companion to InsightWorker: a multi-tenant marketplace where business users discover apps, fill in forms, click Run, and watch results stream into their browser — with no CLI, no .env, no Node install on their box.

It runs at insightaistudio.com (SaaS) or on your own infrastructure (self-hosted). InsightWorker stays the engine; Studio is the surface.

How they relate

	InsightWorker (this product)	InsightStudio (companion)
Audience	Engineers, SREs, devops, technical analysts	Business users — ops, claims, underwriters, PMs
Surface	CLI, VS Code, Desktop app	Browser SaaS
Authoring	Edit `app.yaml`, `workflow.yaml`, prompts/ directly	Visual builder, prompt → app generator, live preview
Execution	On your box, with your secrets	On a worker farm (boxes you bring) — secrets never leave the worker
App format	Bundle (folder with app.yaml + widget.json + workflow.yaml + plan.md + prompts/)	Same bundle — published via `iw app publish` or via Studio's UI builder
Discovery	`iw app pull <slug>`	Marketplace page with tags, descriptions, version history
Run history	Local `runs/` folder per app	Persistent in Studio's DB, queryable per user/org

Why have both?

Same engine, different ergonomics:

Engineers build apps in their editor, iterate fast with the REPL, run locally before publishing.
Business users can't (and shouldn't) install Node or manage .env files. They open a URL, fill a form, get an answer.
The bundle is the contract: an app authored in InsightWorker CLI runs identically in InsightStudio. No conversion, no duplicate maintenance.

Three integration points

1. Publish your CLI-authored apps to Studio

iw app publish uploads your bundle to a shared S3 bucket. Studio's marketplace reads that bucket on a 60s cache TTL and surfaces every published app to its users. See Publish apps to S3.

2. Run Studio's queued jobs on your box

insightworker --worker --studio <url> --token <bearer> turns your InsightWorker into a worker daemon. Studio enqueues runs from its UI; your daemon claims and executes them — with your secrets, your credentials, your skills. See Join a worker farm.

3. Pull a Studio app down to edit locally

iw app pull <slug> downloads any published app to your local apps/ folder. Edit the YAML directly, test with insightworker --ui, then iw app publish a new version when ready.

Architecture — what lives where

┌─────────────────────────────┐    ┌──────────────────────────────┐
│ InsightStudio (browser)     │    │ Author's laptop              │
│  - Marketplace UI           │    │  - InsightWorker CLI         │
│  - App builder              │    │  - Edit bundle locally       │
│  - Runs history             │    │  - iw app publish            │
└──────────┬──────────────────┘    └───────────┬──────────────────┘
           │ enqueues run                       │ uploads bundle
           ▼                                    ▼
┌─────────────────────────────────────────────────────────────────┐
│ Shared S3 bucket    s3://<bucket>/<prefix>apps/<slug>/v<ver>/  │
└─────────────────────────────────────────────────────────────────┘
           ▲                                    ▲
           │ reads bundles                      │ pulls bundle per claim
           │                                    │
┌─────────────────────────────┐    ┌──────────────────────────────┐
│ Studio API (FastAPI)        │◄──►│ Worker daemon                │
│  - PostgreSQL/MySQL state   │poll│ (insightworker --worker)     │
│  - SSE event relay          │ack │  - polls /workers/{id}/poll  │
│  - Worker registry          │    │  - runs CliWorkflowRunner    │
└─────────────────────────────┘    │  - POSTs events back         │
                                   │  - uploads artifacts to S3   │
                                   └──────────────────────────────┘

Capability matching

Workers advertise their installed_skills, credentials, and GPU on register. App bundles can declare requires.skills + requires.creds. Studio's coordinator filters queued runs to workers that meet those requirements — so a claims app needing a Salesforce credential never lands on a worker that doesn't have it.

Get started with Studio

SaaS: sign up at insightaistudio.com. Bring your own worker box and Bedrock/OpenAI key.
Self-hosted: contact contact@verticalserve.com for the enterprise install kit (FastAPI + React + MySQL/Postgres + Alembic migrations).