--- title: Platform Overview description: Manage your bapX account settings, billing, API keys, connectors, MCP configuration, and observability. --- `platform.bapx.in` is the account, billing, connector, API, MCP, and observability control plane for bapX. It is not a second operating workspace. Every account owns a user-level OKF workspace. Businesses live under that user, and newly created or imported repositories always live as projects inside a business: ```text root-sandbox///projects// ``` The public `root-sandbox/` name is the customer-facing workspace boundary. The server-owned storage path remains internal and is not part of the public product contract. Creating an account uses a verified GitHub identity and creates the user workspace and its first business. bapX does not store a password. The device session is shared across the production bapX subdomains and continues until explicit logout, subject to browser cookie retention. Repository authorization remains a separate GitHub App permission flow. The India-first subscription costs **₹500 per month** and includes **5 GB** of storage, hosted search, browser sessions, hosted agents and workflows, Node.js project subdomains, TTS, and STT. Additional storage costs **₹100 per GB per month** up to **100 GB**. Customers bring their own AI-provider and connector credentials. ### Sections - **Account**: Profile, authentication, sessions, and user-level workspace ownership - **Billing and storage**: Razorpay subscription state, included storage, additional storage, and quota limits - **Connectors**: Business-owned external service credentials, including Razorpay for payments - **API keys and MCP**: Programmatic access to approved bapX gateways and MCP servers - **Observability and quality**: Sentry, OpenTelemetry, Braintrust, Vitest evals, agent activity, connector health, and project activity - **Workspace routing**: Business and project destinations used by Agents/Admin Platform manages ownership and configuration. `agents.bapx.in` operates the selected business and project; `admin.bapx.in` uses the same operating model with bapX-wide authority over `/root/bapx.in`. Opening `admin.bapx.in` uses the shared GitHub-backed bapX session, then exchanges a single-use short-lived handoff before granting Admin authority. The server revalidates the configured GitHub provider-ID entitlement before serving the Admin workspace; customer accounts without that entitlement cannot use bapX-wide Admin authority. ### Repository import The Admin Projects surface resolves a GitHub repository through the configured GitHub App before enabling destination editing or import confirmation. It displays GitHub's canonical repository identity, visibility, and default branch, and suggests the non-overwriting Admin destination before mutation. Public repositories can then continue through the existing confirmed import operation. Private repository metadata may be displayed when authorized, but private cloning is not yet enabled and remains disabled in the Admin UI. Changing the repository input invalidates the previous resolution and confirmation. A repository must be resolved again before it can be imported, preventing an earlier response from enabling import for a newer input. ### Agents workspace Opening `agents.bapx.in` requires the same GitHub-backed bapX session. After sign-in, the customer operating surface uses the business main-agent conversation and limits workspace file operations to that account's `root-sandbox//` workspace boundary. The initial hosted main agent streams a connection check, reasoning, and a scoped workspace-status tool result; selecting and storing customer AI-provider credentials remains a Platform-owned configuration step.