Choose what you want to build

Build one managed Agent, test it with real questions, connect only the knowledge and actions it needs, then publish it privately or make a separate deliberate public-access choice. Prostir provides the hosted address, protected access, and delivery into supported AI clients without making you assemble that product backend first.

• One Agent keeps its identity, description, behavior, version, knowledge, memory, and approved actions together as one creator-owned product.
• You can add files and searchable knowledge, Skills, built-in or JavaScript tools, Telegram, WhatsApp, a web widget, and other supported channels.

LimitationsYou want customers to rewrite the Agent's instructions, tools, or shared knowledge.

Keep the method in one portable Skill, validate its structure and references, publish an immutable version, and choose where it belongs: attached to your Agent, used by a Team, downloaded as an archive, or offered separately.

• A Prostir Skill has exactly one root SKILL.md plus optional references, assets, scripts, and evaluation files kept in the same portable product.
• Before publication, Prostir checks metadata, structure, references, unsafe files, and evaluation setup; every published version stays immutable.

LimitationsYou expect Prostir to execute arbitrary scripts from a Skill without a separate trusted runtime.

Use Flow to make the process visible: add triggers and steps, connect them in a graph, review execution settings, and prepare an explicit version. Preview is suitable for evaluating the editor and bounded runs, but it does not present unfinished retry, recovery, or scheduling work as a production guarantee.

• Flow is a separate product with its own identity, slug, mutable draft, visual editor, explicit versions, publication, passport, and portable archive.
• The canvas exposes its step catalog, graph, and selected-step settings; execution keeps events, checkpoints, bookmarks, and incidents with a responsible run owner.

LimitationsYou need a promised replacement for n8n, Zapier, or another established automation runtime.

Create one private Team boundary for membership and roles, a task board, logical data, versioned files, cited knowledge, Skills, MCP connections, and exact references to approved Agents. Shared changes keep actor attribution, revisions, and access checks.

• The available Team foundation uses exact Tenant and Team membership, roles, a private Team host, OAuth, and an installable member-scoped MCP endpoint.
• Shared work now includes Tasks and named boards, Goals, logical databases with tables, views, and records, versioned Files and Documents, cited Knowledge, Skills, Team tools, MCP connections, attached Agents, activity, quotas, and archives.

LimitationsYou want to publish the Team itself as a public Agent or sell it in a marketplace.

Keep the Store as owner of catalog, inventory, cart, order state, and checkout policy. Give one approved Agent narrowly scoped discovery and purchase tools, then publish a Store passport where buyers can browse offers and open the assistant without crossing seller boundaries.

• The current Prostir Store foundation covers catalog, variants, inventory, one-Store carts, checkout and order state, seller fees, Store-scoped customer state, passport, authorized Agent binding, and gated commerce-only MCP. A WebMCP-compatible browser assistant can search and show products from the public Store catalog. The buyer still reviews the order and payment on screen.
• Six Preview connectors have checkout-ready capability paths: Shopify, Square, BigCommerce, WooCommerce, commercetools, and Wix. Exact support remains capability-gated and live third-party-account proof is not universal.

LimitationsYou need every connector to be checkout-ready, universal live-account certification, or every return, refund, administration, and reconciliation lane complete today.