Prostir
Sign in
Get early access

Roadmap

Built. In early access. Planned. The rest waits.

The platform is shipped: sign-in, MCP endpoints for ChatGPT and Claude, Stripe billing, the knowledge graph runtime. The newer work pushes the same agent outward: website widget, Telegram, Slack, e-mail, WhatsApp, Instagram, Facebook Messenger, and Teams. Right now we onboard people one at a time, learn from their builds, and ship improvements before the next person walks in. Public launch follows when the first wave says the flow holds. The long tail stays open until real builds tell us where to dig next.

Get early access
  1. 01 Built

    The platform under the hood

    Sign-in works. Agents get built. Each one gets a stable MCP endpoint on the open internet. The public site speaks eight languages with structured data and llms.txt so answer engines can read it. None of this is the headline. It is what lets the headline exist.

    • Email-code sign-in, profile, settings, and a personal dashboard in six UI languages, built on Blazor WebAssembly.
    • End-to-end agent lifecycle: behavior, knowledge sources, agent-owned JavaScript tools, explicit publish and unpublish.
    • A stable remote MCP endpoint per agent, with versioned variants and knowledge isolation that does not bleed across accounts.
    • Public site in eight languages with case studies, Tech, About, sitemap, structured data, and llms.txt for answer engines.
  2. 02 Built

    ChatGPT, Claude, Stripe, and a knowledge graph that isn't paste

    The integrations people ask about first. ChatGPT and Claude open the agent over MCP. Stripe carries subscriptions and the marketplace. Markdown-LD turns documents into a real knowledge graph, not paste-walls into a prompt. BYOK keeps your provider keys yours.

    • Setup paths for ChatGPT, Claude, Cursor, and other MCP-ready clients in preview. Customer access grants still cover API key, magic link, OAuth, or paid mode. Optional A2A, OpenAI-compatible, Anthropic-compatible, and ChatKit routes sit beside the required MCP path when a creator needs them.
    • Channels now cover Telegram, Slack, e-mail, WhatsApp, Instagram, Facebook Messenger, Microsoft Teams, and the web widget. They do not turn on by magic; the creator connects them on purpose.
    • Provider-aware chat, embeddings, tools, telemetry, and middleware aligned with Microsoft.Extensions.AI on .NET. BYOK provider connections stay encrypted per account; Model Usage Credits cover Prostir-hosted calls when BYOK is not the path.
    • Stripe subscriptions, billable operation visibility, billing portal, webhooks, and plan entitlements pulled from Stripe metadata. Stripe Connect Express marketplace with destination charges, refunds, and payouts.
    • ManagedCode.MCPGateway runtime, Markdown-LD knowledge artifacts, the tool_search, user_memory, and state_machine built-ins, and a management MCP for power users.
  3. 03 In early access
    We are here

    An open waitlist with manual onboarding

    We onboard people one at a time. You write to us, we write back, you build a real agent and put it to work. Your feedback shapes the next improvement before the next person walks in. No anonymous flood. No marketing push before there is something to market.

    • An open waitlist with manual onboarding. No sealed wall, no countdown timer.
    • First users running real agents end to end: behavior, knowledge, tools, customer access. Their agents work, their feedback shapes the next sprint.
    • Improvements shipped from first-wave feedback: MCP try-inspector, knowledge graph management, channel runtime controls, widget streaming, Telegram hardening, model configuration, agent state-machine UX, and a system prompt view with token counts.
  4. 04 Before launch

    Four visible steps

    This is the missing middle: not just saying channels exist, but showing how a creator moves through the launch. The path becomes a few visible moves: choose the first customer surface, connect it, test it with a real person, then decide if the next surface deserves to be added.

    • Step 1: choose the first surface: AI client, website widget, Telegram, Slack, e-mail, WhatsApp, Instagram, Facebook Messenger, or Teams.
    • Step 2: connect access and cost: customer access grants, free access or Stripe price, BYOK or Model Usage Credits.
    • Step 3: run one real conversation end to end, including tools, approvals, channel runtime, and the creator dashboard.
    • Step 4: only then add the next surface. No fake omnichannel launch before the first one holds.
  5. 05 Next

    Public launch when the first wave says it's ready

    Once the first wave ships agents their customers use, the doors open. We won't pin a public date until the first wave says the flow holds end to end. We'd rather slip a quarter than relaunch the same surface twice.

    • Public launch on the same flows the first wave walked: AI-client setup, website widget, messenger channel, paid access, and the creator dashboard on the other side.
    • Agent version history, archive export and import, and flow modules move from build to production rotation.
    • Agent modules go wider: shared agents, A/B variants, and self-learning audit on top of the agent surface.
    • Container deployment polish, the Aspire dashboard, and a public release verification flow that gates a real production push.
  6. 06 Later

    The long tail. No dates yet.

    We aren't writing the long tail until the first batch of real agents shows us where to dig. Real businesses will tell us where the platform needs to go deeper. Until they do, we won't pretend we already know. Everything below is a direction, not a date.

    • Regional and multi-currency pricing with payout routing. The base Stripe currency carries the load for now.
    • Sync beyond snapshots for external knowledge sources, where the source contract permits. No smoke and mirrors.
    • Custom domain MCP endpoints, white-label, SSO, and broader organization controls for teams that outgrow a single account.
    • Operator analytics, audit trails, and cross-agent patterns when more than one team needs them in the same place.

Get on the early list

We aren't waiting for a perfect launch announcement. If your idea wants to be a real AI agent, get on the waitlist and walk the same flow the first wave is walking. We answer by hand. No bot, no autoresponder, no waitlist-position email.

Get early access
  • Tell us what you want to build. One paragraph is enough.
  • Bring one knowledge source, one controlled tool, and one customer access rule or Stripe price. Start small on purpose.
  • Use the case studies as patterns: voice, multi-channel writing, paid expertise, brand-locked images, internal knowledge.

Roadmap

Be one of the first creators

Sign up for early access. We answer by hand, the same flow the first testers walked through.

Get early access