Platform Overview

Pcampus does not sell Starter / Growth / Enterprise packages.
Organizations get Foundation included, then enable commercial services as needed.

Ecosystem

Foundation — included, not sold separately

Identity (PIP) — accounts, organizations, roles, API keys, OIDC · https://pip.pcampus.co
Organization · Console · Developer Platform — the shell, docs, and credentials
Organizations do not “buy Console” or “buy Developer Platform”

Core

PBCP ingests Business Events → Context → Story → Intelligence · https://pbcp-api.pcampus.co
Intelligence lives inside PBCP and is not sold separately — it recommends what to do; it does not send LINE / email / push.
Pulse — operational view: story, current state, next step.

Event tracking and the API's job

PBCP makes business APIs context-aware.
Server is the source of truth; Browser is the source of behavior.
One business fact → one authoritative publisher.

Frontend / App → Customer API → Database / ERP
Customer Backend → POST /events → PBCP
Customer API → Context / Story / Intelligence → the customer's app renders it

• Business facts (order.created, payment.completed) are published from the customer's backend after the business confirms they happened
• Do not embed a production API key in the browser, and do not send order.created from both the page and the backend
• The Event SDK (direction) installs on the server, not the buyer-facing frontend
• Pcampus does not replace the customer's website, app, or checkout — developers pull Story / Intelligence to make existing APIs smarter

Today the path is REST. See Event API

Enableable commercial services

Enable one service at a time on the organization in Console.

Not a SKU yet

Connect and Reward Widget are direction — do not list them in a sell catalog until they can be enabled and priced.

Authentication

All services authenticate with a Bearer token from PIP:

Authorization: Bearer <token>