Evidence → Story → Trust
Business Context that
keeps working.
Pcampus is Product + Platform. PBCP turns business events into Context and Story that Human, Software, and AI can use. Intelligence recommends the next action; your apps or enabled delivery services carry it out.
REST-first today
6 commercial services
Foundation included
pcampus — zsh
$ curl -X POST /v1/events
PulsestoryLive
StoryLive
ContextLinked
Next stepRecommended
ServicesEnable
Business Context·PBCP
Pulse·Operating view
Identity·Included
Notify·Channels
Storage·CDN
Ory Hydra·OAuth2
PostgreSQL·Relational DB
Redis·Caching LayerBullMQ·Job Queues
Kubernetes·OrchestrationMail·Delivery
Content OS·Brand DNA
GitHub Actions·CI / CD
MinIO·Object Storage
Docker·Containers
Sentry·Monitoring
Prometheus·MetricsBusiness Context·PBCP
Pulse·Operating view
Identity·Included
Notify·Channels
Storage·CDN
Ory Hydra·OAuth2PostgreSQL·Relational DBRedis·Caching LayerBullMQ·Job Queues
Kubernetes·OrchestrationMail·Delivery
Content OS·Brand DNA
GitHub Actions·CI / CDMinIO·Object StorageDocker·ContainersSentry·MonitoringPrometheus·MetricsThe Platform Model
Product + Platform.
One learning loop.
One learning loop.
Keep the systems you already run. PBCP sits on top — Evidence becomes Story, Story becomes Trust. Commercial services enable when that context needs delivery.
Layer 01Core products
PBCP is the engine: Event → Context → Story → Intelligence. Pulse is the operating view. Intelligence recommends — it does not send LINE or email itself.
PBCPPulseIntelligence · inside PBCP
↕
Layer 02Commercial services
Enable what the organization needs after PBCP is in the loop. Billing is how we invoice — not a product you sell to end customers.
MailNotifyStorageContent OS
↕
Layer 03Foundation — included
Identity, Organization, Console, and Developer Platform ship with the platform. You do not buy them as separate SKUs. REST is the path today; SDK and CLI are next.
Identity · PIPOrganizationConsoleDeveloper Platform
What is Business Context?
Evidence → Story → Trust.
Business events do not end as logs. PBCP turns them into Context and Story, recommends the next action, then takes the outcome back into context.
Evidence
Event
Fact
Context
Story
Intelligence
Outcome
Loop
Business Context
PBCP Engine
Pulsestory · state · next step
Your appswhere Action happens
Mailif enabled
Notifyif enabled
Storageobjects · CDN
Intelligence recommends. Action runs in your apps or in Mail / Notify you enable — PBCP is not the send channel.
Layer 02 — Core + delivery
PBCP and Pulse at the center.
Delivery when you need it.
Delivery when you need it.
Foundation is included. Enable commercial services on the organization — do not buy Console or Developer Platform as products.
Business Context Platform
PBCP
The core product. Ingest business events as evidence, compose Context and Story, then recommend the next action. Intelligence lives here — it does not send LINE, email, or push itself.
Core product
Pulse
PLS
The operating view for the business team. Open an entity, see the story, the current state, and the recommended next step — without reading infrastructure.
Core product
Identity
PIP
Accounts, organizations, roles, and API keys. Foundation — included with the platform. You do not buy Identity, Console, or Developer Platform as separate products.
Foundation · included
Delivery services
DLV
Action after Intelligence recommends. Enable Mail, Notify, Storage, or Content OS when the organization needs them. Billing is how we invoice — not an engagement product.
Enable per organization
Layer 03 — Developer Experience
REST today.
SDK next.
SDK next.
Start with documentation and REST. CLI and SDK are the goal — not a requirement to ingest events. Production use still enables the commercial service.
REST, then SDK + CLI
Ingest evidence over REST today. TypeScript SDK and CLI are the next direction.
# Path today — ingest a business event
curl -X POST $PBCP_API/v1/events \
-H "Authorization: Bearer $TOKEN" \
-d '{"type":"order.completed"}'
Evidence stored
Context updated
Story composed
# Then GET context / story / intelligence
Contracts
REST is the path today. SDK packages are the goal — not required to start.
REST / docsPath today
@pcampus/pbcpEvents · Context · Story · Intel
@pcampus/identityAuth · Orgs · API keys
@pcampus/mailTransactional + marketing
@pcampus/storageObjects + CDN
Pcampus Developer Docs
API reference, guides, and SDK documentation
→
Layer 01 — Core products
PBCP and Pulse.
Not vertical apps we sell.
Not vertical apps we sell.
The core is Business Context you can operate. Pharmacy, ledger, CRM, retail, and F&B are not the catalog.
PBCP— Business Context Platform
Evidence
Ingested
traceable
Story
Composed
from facts
Intelligence
Recommends
not a send channel
7-day trend
Pulse— Operating view
Story
Timeline
what happened
Current state
Now
why it matters
Next step
Recommended
action elsewhere
7-day trend
Action after Intelligence— not PBCP sending
Evidence ingested
business.event · PBCP
done
Story composed
Context + timeline, traceable
done
Intelligence recommends
next action — decision support
done
Action in your app
or Mail / Notify if enabled
done
Outcome returns
new context for the next loop
loop
PBCP
Live
Pulse
Live
Mail
Live
Storage
Live
Content OS
Live
Notify
Live
Implementation
Live
Founding Pilot
Live
2
Revenue layers — implementation + recurring
6
Commercial services you can enable
4
Foundation layers included
8
Steps in the business learning loop
Foundation — included
Identity and Console ship with it.
You do not buy them.
You do not buy them.
PIP, Organization, Console, and Developer Platform are foundation. The stack below is how we operate that layer — not a catalog of products for sale.
PIPIdentity · orgs · API keys — included
PBCPEvent → Context → Story → Intelligence
NTFNotify — enable when Action needs a channel
STORStorage — objects + CDN, enable per org
Pricing
Enable the services you need.
Pick the services you need — not a Starter / Growth package. Foundation is included. Enabling a commercial service is arranged with sales.
Identity
Organization
Console
Developer Platform
PBCP
Ingest business events, then read aggregated context, composed stories, and recommendations from one API.
Contact salesEvent ingest and evidence
Context API per entity
Story and timeline
Intelligence / next actions
Pulse
See what happened, why, and what to do next — without asking the owner to read infrastructure.
Contact salesStory View on a timeline
Today’s activity Pulse
Recommended next step
Developer Mode evidence
Mail
One delivery path for transactional and marketing email. Other services call Mail instead of sending SMTP themselves.
Contact salesTransactional send
HTML templates
Authenticated domains
Deliverability tracking
Storage
Upload files through one API and serve them on CDN. Apps and Content OS share the same object store.
Contact salesUpload and presign
Org-scoped buckets
CDN delivery
Usage per bucket
Content OS
Turn Brand DNA into platform-native content. Every agent reads brand constraints before it writes.
Contact salesBrand DNA as source of truth
Plan → create → review
Human approval before publish
Analytics into the next plan
Notify
One hub for email, push, SMS, and LINE — templates, preferences, and delivery in one place instead of each app sending on its own.
Contact salesEmail, push, SMS, LINE
Templates per message type
User notification preferences
Sent / delivered / failed tracking
Already have an account? Sign in to browse in Console. Enablement: sales@pcampus.studio
What does Pcampus sell?
Product and Platform around Business Context. Organizations enable PBCP, Pulse, Mail, Storage, Content OS, or Notify. Implementation is connecting events, mapping context and story, and going live — or you install via REST and docs yourself.
Do I buy a package, or enable services?
Pcampus sells commercial services, not Starter / Growth / Enterprise packages. Identity, Organization, Console, and Developer Platform are included. Enable PBCP, Pulse, Mail, Storage, Content OS, or Notify on the organization. Billing is the invoice layer, not a product you sell to end customers. To enable a service, contact sales@pcampus.studio.
Does Intelligence send LINE, email, or push?
No. Intelligence reads Context and Story, then recommends what to do. Action happens in your existing apps, or in delivery services you enable (Mail, Notify). PBCP is not a send channel.
Do I need the SDK or CLI to start?
No. The path today is REST APIs plus documentation. SDK and CLI are the next direction — they may appear on this page as a goal, not as a requirement. Production use still means the organization enables the commercial service.
How do we connect our existing systems?
Keep the systems you already run. Ingest business events into PBCP, then read Context, Story, and Intelligence over REST. If you do not want to own integration, hire PBCP Implementation — scoped to that loop, not a replacement ERP, pharmacy, or ledger.
Is self-hosting available?
On-premises or private-cloud deployment is arranged with the team. Write to sales@pcampus.studio for architecture requirements, deployment automation, and infrastructure support.
Connect existing systems
to Business Context.
to Business Context.
Self-implement over REST, or hire PBCP Implementation. Then enable commercial services as the loop needs them.
Evidence → Story → TrustREST-firstCommercial servicesFoundation included