Weave the
whole site
on one loom.
Loom is a multi-tenant headless CMS and visual website builder, with a news-portal platform underneath. A Studio with 230 plus element schemas and 93 gallery templates, a headless Scribe CMS with GraphQL and REST, and event-based trust scoring. One sign-in via Wenme, built-in bKash and Nagad checkout, one canvas for content and design.
- Section / Row / Column page builder
- Headless CMS, GraphQL + REST
- Bengali typography engineering
- Wenme passkeys, day one
- STUDIOTheme Studio
- SCRIBEScribe CMS
- WWWloom.bd marketing
- APIloom-api
- TRUSTloom-trust
- WORKloom-workers
Counts from the Studio element-catalog documentation and the monorepo workspace listing.
Loom is the headless CMS with a visual builder on top, and a news-portal platform underneath.
Loom pairs a visual Studio (Section, Row, Column, Element, the way Elementor users already think) with a headless CMS (Scribe) and an event-based trust service. Tenants attach a domain, design pages in Studio from 230 plus element schemas and 93 gallery templates, model content in Scribe, and ship. The same canvas builds a news portal, a blog, a portfolio, a service-business site, or a storefront with built-in bKash and Nagad checkout.
The platform is Next.js 16 on the front, Postgres 18 with row-level security for tenant isolation, RabbitMQ for trust events, MinIO for media, and Traefik plus Cloudflare for edge. Authentication is delegated to Wenme (passkeys), authorization to Darwan (policy-based access control), notifications to BitsPath. Loom owns the content, design, publishing, and trust logic on top of that shared core.
Studio. Scribe.
Marketing. Plus the
services beneath.
The Loom monorepo ships three Next.js apps and four backend services in one workspace. Every surface a designer, editor, or platform operator touches is in the same tree, on the same deploy.
- mono-repo
- pnpm workspaces, three Next.js apps, four backend services.
- services
- loom-api, loom-trust, loom-workers, scribe-api.
- data
- Postgres 18 with RLS, Redis cache, RabbitMQ events.
- edge
- Docker + Traefik, Cloudflare for SaaS domains.
- STUDIO
Theme Studio
apps/studioVisual page builder230+ element schemas, 196 documented renderers, 93 gallery templates, drag-drop with dnd-kit, TipTap inline edit, per-breakpoint responsive controls, 3-second auto-save.
- SCRIBE
Scribe CMS
apps/scribe-adminHeadless content backboneSpaces, content types, 18+ field types, GraphQL + REST, localization, preview tokens, scheduled publishing, version rollback, webhooks.
- WWW
loom.bd marketing
apps/wwwPublic siteThe Loom marketing surface is itself built with Loom Studio and managed in Scribe. Dogfood by construction.
The platform decisions that separate Loom from a CMS or a page builder.
Each pillar maps to an app or service in the monorepo. Studio, Scribe, and Trust ship today; the news-portal modules are the active platform rebuild.
Theme Studio
Section, Row, Column, Element.
The hierarchy WordPress + Flatsome + Elementor users already know, in a single rebuilt canvas. 230+ element schemas, 93 gallery templates across 5 categories, auto-save every 3 seconds, per-breakpoint controls, TipTap inline editing.
Scribe headless CMS
Structured content, delivered over API.
Content types with 18+ field types, GraphQL and REST delivery, field-level localization, preview tokens, scheduled publishing, version rollback, webhooks. The CMS and the builder share one canvas, not two integrations.
News-portal platform
Built for Bangladeshi publishers.
The active platform rebuild adds newsroom modules: taxonomy, news models, newsletters, paywall, monetization, UGC, and Bengali typography engineering with per-page font subsetting for fast first paint. In engineering now, on the same core.
Loom Trust
Event-based abuse detection, invisible to visitors.
Order, payment, and fulfillment events flow into a dedicated scoring service (loom-trust) over RabbitMQ. Each account carries a risk band across every Loom tenant. Operators see Low / Medium / High, visitors see nothing.
The headless content backbone, bundled.
Scribe is the headless CMS that ships inside Loom. Content types and 18 plus field types, GraphQL plus REST, field-level localization, preview tokens, scheduled publishing, version rollback, and webhooks. Studio elements render Scribe entries the same way they render any other data-bound block, so a landing page that mixes editorial copy with live structured content is one canvas, not two integrations.
- Content types
- Schema-driven
- Field types
- 18+
- APIs
- GraphQL + REST
- Publishing
- Scheduled + preview
Blog posts
01Rich text, hero, tags, scheduled publishing.
Pages
02Marketing pages, terms, about, contact.
Landing pages
03Campaign-scoped, A/B-ready, template-driven.
FAQ + testimonials
04Structured content rendered by Studio elements.
Loom vs WordPress, Webflow, Contentful.
The honest comparison. Each of these platforms is excellent at what it was built for. Loom is the only one that ships a visual builder, a headless CMS, Bangladesh-local checkout, and cross-tenant trust in a single multi-tenant SaaS.
Scroll for full table
| Capability | Loom | WordPress | Webflow | Contentful |
|---|---|---|---|---|
| Visual page builder included | 230+ elements, Studio | Elementor / Divi add-on | ||
| Headless CMS in the same product | Scribe CMS | CMS Collections (limited) | ||
| Builder pages served as structured JSON over API | Theme-coupled HTML | Hosted rendering | No builder | |
| Cross-tenant trust scoring | ||||
| Multi-tenant SaaS, no plugin maintenance | ||||
| Passwordless auth (passkeys / WebAuthn) | Wenme, default | Plugin | SSO add-on | |
| Bangladesh payments (bKash, Nagad) | Built-in checkout | Plugin-per-gateway | ||
| Self-hosted on customer infra (sovereign data) | Docker + Traefik |
Capability claims for WordPress, Webflow, and Contentful based on public documentation as of 2026 Q2. Speak to vendors for current matrices.
Four steps from passkey sign-in to a published site.
The launch flow assumes zero hosting knowledge. Most single-site tenants reach publish on the same afternoon they sign up. Custom domains add a DNS round-trip; the platform subdomain works instantly.
- Step 01
Sign in with Wenme
One button. Passkey or magic link. Tenant is auto-provisioned, default theme cloned, Scribe space created in a single workflow.
- Step 02
Attach a domain
Add a custom domain in the tenant dashboard. Loom emits a TXT record, the background worker verifies it, then Traefik issues SSL through Cloudflare for SaaS. The platform subdomain works the moment the tenant is born.
- Step 03
Design in Studio
Start from one of 93 gallery templates or drag from the 230+ element catalog onto the Section / Row / Column canvas. Auto-save runs every three seconds. Per-breakpoint controls let one layout cover mobile, tablet, and desktop without forks.
- Step 04
Model content and publish
Define content types in Scribe, write with TipTap inline editing, schedule publishing. Sites that sell take payments through the built-in bKash and Nagad checkout. Hit publish and the site serves over Next.js ISR.
Built on the platform we already operate.
Loom is a KaritKarma product. Authentication, authorization, communications, and payments are inherited from the shared core so the Loom team can focus on content, design, publishing, and trust.
Modern, boring, multi-tenant.
Every piece of the stack is something a Bangladeshi DevOps engineer can hire for and a regulator can audit. No managed-only lock-in.
- Backend.NET 10 services; single-binary Go rebuild in engineering
- FrontendNext.js 16, React 19, TypeScript 5.9, Tailwind 4
- DataPostgreSQL 18, RLS tenant isolation, Redis 8
- MessagingRabbitMQ 4.2, event-sourced trust pipeline
- StorageMinIO S3-compatible, imgproxy on-the-fly transforms
- EdgeTraefik + Cloudflare, wildcard SSL, custom-domain attach
Questions teams ask before they migrate.
Each answer mirrors the on-page text in the structured-data payload, so AI answer engines and procurement reviewers see the same wording.
- 01What is Loom?
- Loom is KaritKarma's multi-tenant headless CMS and visual website builder, with a news-portal platform underneath. It pairs the Studio visual builder (230+ element schemas, 93 gallery templates) with the Scribe headless CMS (content types, 18+ field types, GraphQL + REST) and an event-based trust scoring service. Tenants sign in with a Wenme passkey, attach a domain, design pages in Studio with the same Section / Row / Column hierarchy that Elementor users already know, model content in Scribe, and take payments through the built-in bKash and Nagad checkout. The platform runs Next.js 16 on the front, Postgres 18 with row-level security for tenant isolation, behind Traefik with Cloudflare for SaaS.
- 02How does Loom compare to Sanity, Contentful, and Strapi?
- Sanity, Contentful, and Strapi are headless CMSes only. Loom ships Scribe (a headless CMS comparable to those three, with content types, GraphQL + REST, localization, preview tokens, scheduled publishing) and pairs it with a visual Studio, multi-tenancy, news-portal modules, and a trust layer in the same product. If you only need a CMS, Sanity is excellent and we say so. If you need a CMS plus a designer-friendly canvas plus Bangladesh-local payments and publishing engineering, Loom is the only single-vendor option in this category in Bangladesh.
- 03How does Loom compare to WordPress?
- WordPress is the platform most Bangladeshi site owners migrate from. Loom intentionally mirrors its Section / Row / Column page-builder UX so the muscle memory transfers, but removes the plugin chaos and the security-patch treadmill by running as a multi-tenant SaaS: one curated platform, one upgrade train. The CMS is headless by construction (builder pages serve as structured JSON over an API rather than theme-coupled HTML), and a cross-tenant trust score travels with accounts in a way standalone WordPress installs cannot reproduce.
- 04Can Loom render at the edge?
- Published pages are served by Next.js 16 with ISR (incremental static regeneration), fronting every site with cached pages that revalidate against Scribe and Loom API events. Traefik terminates SSL at the platform edge with Cloudflare for SaaS handling custom-domain SSL provisioning. The backend API never renders HTML on the request path; it serves builder page-JSON and content over GraphQL and REST, so no visitor waits on a cold database round-trip for page chrome.
- 05What does the news-portal platform add for publishers?
- The active Loom platform rebuild is publisher-first: taxonomy and news content models, newsletters, paywall and monetization modules, UGC, webhooks, and i18n. Its standout engineering is Bengali typography: per-page Bengali font subsetting (HarfBuzz-grade shaping with TTF subset emission) so a Bangla news page ships only the glyphs it uses, cutting font payload for faster first contentful paint. These modules are in engineering now on the same multi-tenant core that runs Studio and Scribe.
- 06How does multi-tenancy work, and is data really isolated?
- Every tenant-scoped table includes a tenant_id column and is protected by PostgreSQL row-level security policies, so cross-tenant queries are impossible at the database layer, not just at the API layer. The API middleware injects tenant context from either the JWT or a domain-to-tenant lookup cached in Redis. Sites resolve to a tenant by custom domain (Cloudflare proxy mode through Traefik) or by platform subdomain. Studio, Scribe Admin, and the public sites all run on the same RLS-guarded core, so an operator cannot accidentally read another tenant's pages or orders.
One canvas for
content and design.
Loom is live at loom.bd. Pair it with Wenme, Darwan, and BitsPath from the KaritKarma platform, with bKash and Nagad checkout built in. One vendor, one deploy, one tenant model.