ContextHub Cloud overview
This guide is for customers building on the managed ContextHub SaaS at ctxhub.net. It documents the operated API, tenant boundary, delivery patterns, and managed capabilities available through ContextHub Cloud. It is not a promise that every described service exists in the community repository.
ContextHub Cloud is operated by İKONX Bilişim ve Tarım Sanayi ve Ticaret Ltd. Şti. See Legal, service, and merchant identity for the relationship between ctxhub.net, the corporate domain ikon-x.com.tr, subscription terms, privacy, and billing roles.
Service boundary
ContextHub Cloud combines the core content platform with operated infrastructure and commercial services.
| Area | ContextHub Cloud responsibility |
|---|---|
| Content platform | Tenant-aware content, collections, media, galleries, menus, forms, roles, and admin workflows |
| Personalization | Placement decisions, targeting rules, weighted experiences, A/B-test reporting, funnels, realtime analytics, and journeys |
| API edge | https://api.ctxhub.net routing, tenant CORS, origin protection, and public/private route policy |
| Managed delivery | Hosted API operations, media delivery, monitoring, upgrades, and support |
| Managed capabilities | Plan-dependent services such as Semantic Search and commercial plugins |
The public repository contains the open-core platform and extension contracts. The ctxhub.net service also includes operated infrastructure, private companions, configuration, and commercial capabilities that are not shipped as community-repository features.
Integration model
Your browser or server
|
v
https://api.ctxhub.net
ContextHub Edge Gateway
|
v
Tenant-scoped ContextHub Cloud services
Use a server-side ctx_... API token for authenticated content, media, schema, and management reads. Use deliberately public /api/public/* routes with X-Tenant-ID for browser delivery. Never embed an API token in browser JavaScript.
Choose the right resource
- Content is for editorial pages, articles, announcements, and reusable narrative records.
- Collections are for typed repeatable data such as locations, people, products, events, or FAQs.
- Media manages uploaded files, image variants, accessibility metadata, and external video records.
- Menus describe navigation trees.
- Forms describe input schemas and collect submissions.
- Placements are personalization and experimentation surfaces with rule-based decisions, weighted experiences, frequency controls, event collection, A/B tests, funnels, and journeys.
What differentiates ContextHub Cloud
- Multi-tenant memberships and custom roles support agency/client separation in one control plane.
- Forms and galleries are first-class managed resources, not fields improvised inside generic entries.
- Placements combine personalized delivery, experimentation, and analytics without requiring a separate optimization product.
- The public Plugin API lets trusted extensions add APIs, consumers, settings, entitlements, and admin surfaces without forking core.
- Dashboard, activity, token, and feature-flag APIs let agencies build their own operational workflows.
Recommended production path
- Create the tenant and configure allowed browser origins in ContextHub Cloud.
- Create a least-privilege, expiring API token for server-side integration.
- Model editorial information with Content and structured records with Collections.
- Add a 30–60 second application cache for safe reads.
- Invalidate affected cache keys from verified webhooks.
- Add tenant roles, audit export, and token rotation to the operating checklist.
- Ask ContextHub about plan-dependent managed capabilities before building against them.
Continue with Quickstart, Placements and personalization, and Roles and permissions.