Skip to content

What you can build with Doable

Doable is a collaborative AI workspace where your team designs, codes, and publishes side by side. "App" is just one of many things you can create here. Every project becomes an artifact: a self-contained thing you and your teammates can edit, share, publish, export, or list on the marketplace.

This page tours every kind of artifact Doable supports today, where to make it, and how to put it in front of other people.

Web apps

What it is. A full-stack web app, typically Next.js + React + Tailwind, generated and edited live by the AI in a sandboxed dev server.

Where to make it. Dashboard → New Project → pick a template (or start blank) → Web app.

What you can do with it.

  • Iterate by chatting with the AI in the editor; it edits files, runs builds, and previews live.
  • Co-edit with teammates in real time (Yjs/CRDT).
  • Wire it to integrations, Supabase, your own MCP servers, or external APIs.

How to share it. Publish to a Doable subdomain or your own custom domain (see Publishing). Optionally list the result on the Marketplace.

Example. "Build me a Kanban board with drag-and-drop and a Supabase backend" ships as my-board.doable.me in minutes.

Progressive Web Apps (PWAs)

What it is. A web app that installs on phones and desktops like a native app, works offline, and can send push notifications, but ships from the same Doable project as your website.

Where to make it. Dashboard → New Project → enable the PWA option in project settings, or ask the AI in chat for "a PWA version of this site." Doable wires up the service worker, manifest, and install prompt for you.

What you can do with it.

  • Ship the same artifact to web and mobile without an App Store review.
  • Cache pages and assets for offline use.
  • Send push notifications once you connect a provider.
  • Add to home screen on iOS, Android, Windows, and macOS.

How to share it. Publish like any other Doable site; visitors get the "Install app" prompt in supported browsers. Custom domain works too.

Example. A field-service checklist PWA that your crew installs on Android and uses offline at the job site.

Visual assets: business cards, flyers, posters, social cards

What it is. Print- and share-ready visual artifacts: a business card, an event flyer, a conference poster, a social-media card. Designed in the same canvas as the rest of Doable, but optimized for a specific output size and exported as PDF or PNG.

Where to make it. Dashboard → New Project → Visual asset → pick a size preset (business card, A4 flyer, A3 poster, Instagram square, story, banner, etc.). Or describe what you want ("a poster for our launch party, dark theme with neon accents") and the AI builds it.

What you can do with it.

  • Design in the live canvas with the same Visual Designer used for websites.
  • Co-design with teammates in real time; drop comments where the headline should land.
  • Re-skin from a brand kit (logos, fonts, palette) loaded into the workspace.
  • Export to PDF for print or PNG for social.

How to share it. Publish the live web version as a "share link," or export and send. Reuse the design as the hero for the matching landing page so your print, web, and social look identical.

Example. Your team designs a launch flyer Monday morning, exports the PDF for the print shop, then turns the same layout into a landing page and an Instagram card before lunch.

Static sites

What it is. A pure HTML/CSS/JS artifact with no server runtime, perfect for landing pages, docs, portfolios, or any content-first site.

Where to make it. Dashboard → New Project → File Builders / Static template, or ask the AI in chat for "a static landing page."

What you can do with it.

  • Author with the File Builders and Visual Edit tools.
  • Drop in Markdown, images, or your own assets.
  • Build once, serve cheaply. Caddy hosts the artifact directly with zero runtime cost.

How to share it. Publish via the same flow as web apps. Doable detects static output and serves it through Caddy. Add a custom domain when you're ready.

Example. A one-page launch site for your indie game, published to mygame.doable.me.

MCP apps

What it is. A Doable project that is itself an MCP App: a UI surface that plugs into MCP-compatible hosts (Claude, IDEs, agent runners) so the host can drive your app's tools and resources.

Where to make it. Dashboard → New Project → start a Web app and enable the MCP App surface in project settings, or scaffold from an MCP App template when available. The runtime is implemented in services/api/src/mcp/ and exposed through services/api/src/routes/chat/mcp-call.ts.

What you can do with it.

  • Expose your app's actions as MCP tools so any MCP host can call them.
  • Serve resources (files, datasets, live data) over MCP.
  • Re-use the same artifact as both a hosted website and an MCP-driven surface.

How to share it. Publish like a normal app, then point your MCP host at the published URL. Listing on the Marketplace lets other users discover it.

Example. A "Customer CRM" MCP app that Claude can read from and write to from inside your editor.

Custom skills

What it is. A reusable, scoped instruction or capability that the AI can call by name. Think "Doable's slash-commands for your workflow." Backed by services/api/src/routes/skills.ts.

Where to make it. Editor → Skills panel → New Skill, or via the API. Skills can be personal or workspace-scoped.

What you can do with it.

  • Codify recurring prompts (e.g. "review this PR", "rewrite copy in our brand voice").
  • Bundle tool calls into one named action.
  • Share with your workspace so every teammate gets the same shortcut.

How to share it. Workspace skills are auto-shared with members. Publish skills as part of a Marketplace listing to share them outside your workspace.

Example. A release-notes skill that reads recent commits and drafts a changelog entry.

MCP servers

What it is. A connector (built-in or user-added) that exposes external tools, APIs, or services to the AI as MCP tools. See services/api/src/mcp/builtin-connectors.ts.

Where to make it. Workspace Settings → Integrations → MCP servers → Add server (for hosted MCP endpoints) or use one of the built-in connectors.

What you can do with it.

  • Plug in Supabase, GitHub, Stripe, custom HTTPS MCP servers, and many more.
  • Let the AI call those tools in chat without leaving the editor.
  • Combine with Integrations to grant scoped credentials.

How to share it. MCP server configs travel with the workspace; admins can install once for everyone.

Example. Add a Supabase MCP server so the AI can query and migrate your database.

Knowledge bases

Coming soon

Doable plans to ship project-scoped knowledge bases (chunking, embeddings, vector search) as a first-class artifact. Today, you can approximate this by uploading files into a project and asking the AI to read them, or by pointing an MCP server at your documents.

Templates

What it is. A reusable project scaffold (files, config, AI prompts) that anyone can fork to start their own artifact. Backed by services/api/src/routes/templates.ts.

Where to make it. Open an existing project → Project menu → Publish as template, then submit it to the marketplace from the template's page.

What you can do with it.

  • Turn a polished app into a one-click starter for your team or the community.
  • Pin a curated stack (framework, integrations, skills) for newcomers.
  • Earn marketplace credibility as a template author.

How to share it. Submit through the Marketplace submit flow; once approved it shows up in New Project → Templates for everyone. See Marketplace.

Example. A "SaaS starter with Supabase auth + Stripe billing" template that ships with the skills and MCP servers pre-wired.

Integrations

What it is. A scoped credential + adapter that lets your app or the AI talk to a third-party service (Google, Slack, Notion, 600+ more via Activepieces pieces).

Where to make it. Workspace Settings → Integrations → Add integration. See Integrations for the full catalog and how OAuth flows work.

What you can do with it.

  • Authorize once at workspace level; reuse across every project.
  • Call integration actions from chat, skills, or your app's runtime.

How to share it. Integration credentials stay vaulted in your workspace; teammates inherit access by role. You can publish integration recipes via templates or marketplace listings.

Example. Connect Gmail once, then have the AI draft and send release emails from any project.

Marketplace listings

What it is. Any artifact (app, template, skill, MCP app) packaged for discovery and install by other Doable users.

Where to make it. Project / Template / Skill → Publish → Submit to Marketplace. See Marketplace for submission guidelines.

What you can do with it. Reach the broader Doable community, accept forks, and optionally monetize once billing is enabled.

How to share it. It's already shared the moment it's listed; others install with one click.

Example. A "Daily Standup Bot" MCP app, listed publicly with a one-click install.

Published websites

What it is. The live, externally-reachable version of a web app, static site, or MCP app, served from *.doable.me or your custom domain.

Where to make it. Project → Publish → choose subdomain or custom domain. See Publishing for the full flow and Custom Domains for DNS setup.

What you can do with it.

  • Get a shareable HTTPS URL via Cloudflare Tunnel (no port forwarding, no SSL hassle).
  • Bring your own domain and let Caddy + Cloudflare handle TLS.
  • Roll back to any previous publish at any time.

Example. Promote your prototype as acme-prototype.doable.me, then upgrade to prototype.acme.com for the demo.

Artifact-by-artifact quick reference

Artifact Typical creator Typical use-case
Web app Founder, designer, indie hacker SaaS prototypes, internal tools
Progressive Web App Founder, ops, field teams Installable apps for web + mobile, offline tooling
Visual asset Designer, marketer, event organizer Business cards, flyers, posters, social cards
Static site Marketer, writer Landing pages, docs, portfolios
MCP app Developer, agent builder App surface for Claude / MCP hosts
Custom skill Power user, team lead Reusable prompts and macros
MCP server Workspace admin Connect external APIs to the AI
Knowledge base Researcher, PM Searchable docs (coming soon)
Template Community author One-click starter for newcomers
Integration Workspace admin Vaulted credentials for SaaS APIs
Marketplace listing Any creator Distribution to the Doable community
Published website Anyone Public URL for a finished artifact

Ready to ship one? Start in the Editor, then head to Publishing or Marketplace when it's ready for the world.