PBCP — Business Context Engine
One Business Context.
Every Platform Service.
Define your business once — customers, branches, permissions, products. Every service: Identity, Billing, Workflow, and Notifications operates on that same context automatically.
All systems operational
6 platform services
Thai-hosted
pcampus — zsh
$ pcampus create pharmacy
ConsolepharmacyLive
Users847
Orgs12
Events/d2.1M
Storage1.2 TB
Identity Platform·PIP
Business Context·PBCP
Notifications·5 Channels
File Platform·CDN
Ory Hydra·OAuth2
PostgreSQL·Relational DB
Redis·Caching LayerBullMQ·Job Queues
Kubernetes·OrchestrationPharmacy·Healthcare
PBCP Cockpit·Analytics
Billing·Payments
Ledger·Accounting
GitHub Actions·CI / CD
MinIO·Object Storage
Docker·Containers
Sentry·Monitoring
Prometheus·MetricsIdentity Platform·PIP
Business Context·PBCP
Notifications·5 Channels
File Platform·CDN
Ory Hydra·OAuth2PostgreSQL·Relational DBRedis·Caching LayerBullMQ·Job Queues
Kubernetes·OrchestrationPharmacy·Healthcare
PBCP Cockpit·Analytics
Billing·Payments
Ledger·Accounting
GitHub Actions·CI / CDMinIO·Object StorageDocker·ContainersSentry·MonitoringPrometheus·MetricsThe Platform Model
One ecosystem.
Three layers.
Three layers.
Every application shares the same foundation. Build on top — never rebuild underneath.
Layer 01Business Applications
Domain-specific apps built on the platform. Each ships in weeks, not months — because Identity, Billing, Workflow, and Notifications are already wired in.
PharmacyPBCP CockpitBillingLedgerRetail — soonF&B — soon
↕
Layer 02Platform Services
Four shared services every application uses automatically. No duplication — every team writes zero auth code, zero notification logic, zero file handling.
Identity · PIPBusiness Context · PBCPNotifications · NTFFile Storage · FIL
↕
Layer 03Infrastructure Foundation
Battle-tested technology owned and operated by the platform team. Applications never touch this layer directly — zero Kubernetes config, zero database tuning.
Ory Hydra · KratosPostgreSQLRedisMongoDBMinIOBullMQKubernetes
What is Business Context?
Define once.
Every service understands.
Every service understands.
You describe your business — its customers, branches, employees, and products. Every service reads that same context automatically. No re-integration. No drift.
Customer
Branch
Employee
Permission
Order
Product
Inventory
Invoice
Business Context
PBCP Engine
Identitystaff · customers · roles
Billinginvoices · payments
Workflowtasks · approvals
NotificationSMS · Push · Email
Storagefiles · CDN
Every service automatically inherits your business structure — no extra configuration.
Layer 02 — Platform Services
Shared infrastructure.
Zero duplication.
Zero duplication.
Every application in the ecosystem uses the same four services. Build fast because the hard engineering is already done.
Identity Platform
PIP
Authentication, organizations, members, roles, and OAuth2/OIDC management. Powered by Ory Hydra and Kratos. Every Pcampus product shares one identity layer.
10M+ tokens / day
Business Context Platform
PBCP
Collects events, builds customer stories, and delivers business intelligence. Powers Cockpit analytics and segment-driven decisions across the ecosystem.
847k+ events / day
Notification Platform
NTF
Unified multi-channel delivery for every product. Email, push, SMS, and LINE — no application builds this twice. One API, all channels.
5 channels
File Platform
FIL
Upload, storage, CDN delivery, and document management. One API for all file operations across the entire ecosystem. Backed by MinIO and a global CDN.
1 TB+ served
Layer 03 — Developer Experience
One CLI. One SDK.
One way to ship.
One way to ship.
Every team uses the same tools, contracts, and standards — regardless of which product they're building.
Pcampus CLI + SDKs
Scaffold, develop, and release any Pcampus application from one toolchain.
npm install @pcampus/identity
import { PcampusIdentity } from '@pcampus/identity'
newconst pip = PcampusIdentity({
process.env clientId:.PIP_CLIENT_ID,
process.env issuer: .HYDRA_ISSUER,
})
const session = await pip.verifyToken(token)
// { sub: '...', orgs: [...], roles: [...] }
SDK Packages
Type-safe clients for every platform service.
@pcampus/identityAuth + Orgs + RBAC
@pcampus/pbcpEvents + Context + Intel
@pcampus/notificationAll channels
@pcampus/storageFiles + CDN
@pcampus-studio/uiDesign system
Pcampus Developer Docs
API reference, guides, and SDK documentation
→
Layer 01 — Real Products
Production software.
Not illustrations.
Not illustrations.
Applications solving real Thai business problems — all built on the same platform layer.
Pharmacy— Healthcare Management
Daily Sales
฿45,230
+12.4%
Inventory
2,847 items
-3 low stock
Patients today
127
+8 new
7-day trend
PBCP Cockpit— Business Intelligence
Events today
847,234
+22.1%
Active segments
12
3 updated
Active users
3,421
+4.8%
7-day trend
Notification Platform— delivery trace
Event emitted
patient.prescription.ready · PBCP
sent
Channel routing
push · LINE · email fallback
sent
Push delivered
FCM token · 0.3s
sent
LINE sent
channel_id: C8F2... · 0.6s
sent
Email queued
SMTP fallback · scheduled 5m
queued
Pharmacy
Live
Cockpit
Live
Billing
Live
Ledger
Live
Retail
Soon
F&B
Soon
Manufacturing
Soon
Education
Soon
847k+
Events processed daily
4
Shared platform services
99.9%
Uptime SLA target
12+
Battle-tested infra components
Foundation — Infrastructure
Battle-tested technology.
Platform teams own it.
Platform teams own it.
Business applications talk to clean platform APIs. The platform team manages every infra concern — from Ory Hydra auth to MinIO object storage.
PIPOry Hydra · Ory Kratos · PostgreSQL · Redis
PBCPMongoDB · Redis · BullMQ · PostgreSQL
NTFBullMQ · Redis · SMTP · Firebase · LINE
FILEMinIO · PostgreSQL · CDN · Redis
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: [email protected]
How does Pcampus differ from building infrastructure in-house?
Building auth, event tracking, notifications, and file handling from scratch takes months and requires constant maintenance. Pcampus provides all four as production-ready shared services with a single integration point. You write business logic — we handle the platform.
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 Pulse, PBCP, Mail, Storage, Content OS, or Notify on the organization billing account. Invited users receive trial credit instead of a Free plan. To enable a service, contact [email protected].
How does authentication work with PIP?
PIP is built on Ory Hydra (OAuth2/OIDC server) and Ory Kratos (identity management). Your application registers as an OAuth2 client and receives standard JWT access tokens with org and role claims. No custom auth code needed.
Can Pcampus be used for non-Thai businesses?
The platform is language and region-agnostic. The LINE notification channel and certain compliance features are Thai-focused, but authentication, event tracking, file storage, and the developer tooling work globally.
How do I migrate an existing application to Pcampus?
Use the Pcampus CLI to register your app as an OAuth2 client, then migrate services one at a time. Start with PIP for authentication, then add PBCP event tracking. Full migration guides are in the developer documentation.
Is self-hosting available?
On-premises or private-cloud deployment is arranged with the team. Write to [email protected] for architecture requirements, deployment automation, and infrastructure support.
Build once.
Deploy everywhere.
Deploy everywhere.
Join the Pcampus platform. One identity, four shared services, and a developer experience designed for speed.
Shared IdentityUnified EventsOne Developer CLINo Duplicate Infra