---
title: Why bapX?
description: One operating system for people, projects, and specialist agents, with explicit live and planned boundaries.
---

**bapX** is an operating system for people and agents. It combines a GitHub-backed workspace boundary, an authenticated customer operating surface, a central main-agent runtime, and a public TypeScript framework for agents and workflows.

## What is live today

- **Public product and documentation** — The landing, pricing, ecosystem, documentation, research, release, and MediaHub routes are served from one versioned web release.
- **GitHub-backed identity** — A verified GitHub identity creates or resumes the account and user-level OKF workspace. Repository authorization remains a separate GitHub App permission flow.
- **Customer operating surface** — `agents.bapx.in` is authentication-gated and uses the shared operating shell, central main-agent transport, and customer-scoped workspace routes.
- **bapX Admin** — `admin.bapx.in` is entitlement-gated and applies the same operating model with wider bapX workspace authority. Confirmed public-repository import is implemented.
- **Developer framework** — Code-defined agents, workflows, tools, skills, channels, persistence, Node.js and Cloudflare targets, the runtime API, and SDK have public documentation.
- **Enterprise delivery** — [MediaHub](https://mediahub.bapx.in) offers direct, custom-quote forward-deployed engineering for AI/data/CRM/ERP, commerce, growth, and managed production outcomes.

## What remains incomplete

Platform currently supplies authentication and the control-plane information architecture. Self-service provider credential management, connector setup, API-key management, MCP client management, billing checkout, quota enforcement, team-role administration, arbitrary hosted-agent creation, and one-click project hosting are not yet complete public workflows.

The shared `api.bapx.in` API and MCP gateway is also not served today. The framework API documentation describes APIs exposed by applications that developers build and deploy; it does not advertise a live shared bapX gateway.

## Where bapX is focused

bapX begins with operating work its team already understands deeply:

- Brand, campaign, content, and media operations
- Product, engineering, support, and business delivery
- Projects, approvals, evidence, and human-agent coordination
- Enterprise integrations that require embedded builders rather than advisory reports

## Product principles

1. **Evidence before availability** — A capability is shipped only after merge, deployment, and live verification.
2. **Scoped workspaces** — Customer work remains inside the authorized user, business, and project boundary.
3. **Bring your own credentials** — Provider and connector credentials belong to the customer or business scope; bapX does not promise pooled third-party quotas.
4. **One operating model** — Agents and Admin use the same people, project, agent, automation, and evidence concepts with different authority.
5. **Clear commercial boundaries** — The Agents subscription and direct MediaHub enterprise engagements are separate offers.

## Pricing

The India-first Agents offer is ₹500/month with 5 GB storage, hosted search, browser sessions, hosted agents/workflows, TTS, STT, and Node.js project subdomains included when project hosting is enabled. Self-service subdomain publishing is not currently available. Additional storage is ₹100/GB/month up to 100 GB. There is no free bapX plan. Automated billing and quota controls remain incomplete until they are deployed and verified.

Review [Product surfaces and availability](/docs/introduction/product-surfaces/) before depending on a specific hosted workflow, or open the [Development overview](/docs/reference/development/) to build with the framework today.