With Kanorio, you can present your brand website in two ways:
Best of all: Both modes share the same Kanorio backend. Even if the frontend is built by engineers or AI, your operations team can still modify articles, view orders, manage customers, and review all data in the "Data & Collections › Tables" workspace daily—without ever touching a line of code.
When evaluating whether Kanorio supports your needs (e.g., brand site + blog, online course platform, or membership site), you can check the Capability Support Matrix (/developers/capabilities), which is generated in real-time:
| Capability Domain | Current Status | Guides & References |
|---|---|---|
| 1. Content (Pages, Navigation, Blog, Custom Data Collections) | Fully Supported | · Delivery API Reference |
| 2. Customers & Members (Contacts, Dynamic Segments, Passwordless Login, Access Control) | Fully Supported (Membership tiers in planning) | · Customer API Reference |
| 3. Credits & Stored Value (Store Credit, Pass Ledgers) | In Planning | View support status overview |
| 4. Products & Promotions (Products, Variants, Categories, Discount Rules) | Fully Supported (Checkout hosted by system) | Delivery API Reference · Management API Reference |
| 5. Bookings & Resources (Time slots, Staff & Equipment Booking) | In Planning | View support status overview |
Once you set an "External Storefront URL (externalStorefrontUrl)" to redirect traffic to your custom frontend, certain features that rely on the hosted page DOM or hosted traffic (e.g., backend "SEO › Site Speed" measurement, "Marketing › In-site Promotion" banners and pop-ups, editor-based font/color styling, auto-generated sitemap.xml, and first-party traffic analytics) will only work on Kanorio-hosted pages.
We have documented every hosted-only feature and its corresponding alternative for custom frontends (Next.js/Astro) in the Capability Support Matrix — Hosted-only section.
When building your own frontend, please identify where each of the three credentials applies:
https://{your-site}/api/v1/*. Browsers can fetch directly. Read-only draft previews require your server-side to include the X-Kanorio-Preview: knr_pv_... preview token.knr_cat_): Obtained after a buyer logs in via <kanorio-login> or /api/v1/customer/auth/* on your frontend. This represents the buyer's commercial entitlement.knr_pat_): Represents your or your team's backend operational permissions (RBAC). This must only be stored server-side, in CI/CD, or in AI tools. Never expose this in browser code.When your frontend is deployed on an external platform (e.g., https://www.brand.com on Vercel), you usually do not want to click "Publish" on the default Kanorio template pages, as this would compete with your official site for search engine indexing.
You can complete your headless deployment via three settings in "Site Settings › Developer". Once configured, the site status card on your "Dashboard" will automatically switch to "API Service Active", displaying your external frontend URL and system API URL:
systemHost): Every site is assigned a permanent system URL (https://s-xxxxxxxxxxxx.kanorio.com) upon creation, which is ideal for use as the API base URL in your external frontend environment variables.headlessEnabled): When enabled, https://{system-url}/api/v1/*, blog publishing, and customer login will function even if the hosted site remains unpublished.externalStorefrontUrl): When set, visitors who land on Kanorio subdomains will be automatically redirected via 302 to your external main site. The "Preview Site" button on the dashboard will also automatically open your external frontend with a short-term preview token.You can ask your AI assistant to enable this for you:
Please enable Headless mode for this site (headlessEnabled: true), set the external storefront URL to https://www.example.com, add https://www.example.com to allowedOrigins, and tell me the permanent system URL (systemHost) for this site.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Content Delivery API Calls & Bandwidth | Unlimited, no bandwidth fees | Unlimited, no bandwidth fees | Unlimited, no bandwidth fees |
| Custom Data Collection Entries (Includes drafts; paid plans can add per 1,000 entries) | 50 entries | 1,000 entries (add up to 20,000) | 10,000 entries (add up to 200,000) |
Blog Post Publishing & blog* System Collection API | Drafts only | Open (does not count towards custom collection limit) | Open (does not count towards custom collection limit) |
| Online Courses & Digital Deliverables (Deliverables & Elements) | Open | Open | Open |
| Webhook Endpoint Count (Business plan supports filtering by collection or form) | — | Up to 3 endpoints | Up to 10 endpoints (supports event filtering) |
| Total Storage Space | 200 MB (shared across account) |
No. The blog* collection and system tables like products, orders, contacts, and deliverables are completely excluded from the 50/1,000/10,000 custom data collection limits.
Yes, with zero migration cost. The pages, data collections, blog posts, products, deliverables, and online forms you create in the backend are already served via {your-site}/api/v1/*. You can seamlessly switch at any time by building a new frontend and setting the externalStorefrontUrl.
| 6. Orders & Forms (Transactions, Online Forms & Anti-spam Submission) | Fully Supported | · Delivery API Reference |
| 7. Delivery (Online Courses, Downloadable Packages, 600s Signed Playback, Learning Progress) | Fully Supported (Includes <kanorio-*> components) | · Elements Reference |
| 10 GB (add-ons available) |
| 200 GB (add-ons available) |