Weave the
whole store
on one loom.

Questions sellers 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 website builder and commerce operating system. It pairs a visual Studio with 230+ live elements, a headless Scribe CMS, a B2B supplier catalog that feeds B2C seller stores, and an event-based trust scoring service. Sellers attach a domain through Wenme passkey sign-in, design pages in Studio with the same Section / Row / Column hierarchy that Elementor users already know, pull product truth from the supplier catalog, and route payments through LoneSock Pay. The platform is .NET 10 backend, Next.js 16 frontend, Postgres 18 with row-level security for tenant isolation, packaged as Docker Swarm services behind Traefik.

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, a commerce engine, multi-tenancy, 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 storefront plus a designer-friendly canvas plus B2B-to-B2C distribution, Loom is the only single-vendor option in this category in Bangladesh.

03How does Loom compare to WordPress + WooCommerce?

WordPress + WooCommerce is the platform most Bangladeshi sellers migrate from. Loom intentionally mirrors its Section / Row / Column page-builder UX so the muscle memory transfers, but replaces the plugin chaos with a curated module system, removes the security-patch treadmill by running multi-tenant SaaS, and adds two things WordPress cannot: a shared B2B catalog every seller can reference instead of re-keying SKUs, and a cross-store trust score that travels with the customer. CSV importers from WooCommerce, Shopify, OpenCart, and ZenCart are on the platform roadmap (Phase 6.2-6.3).

04Can Loom render at the edge?

Storefront pages are served by Next.js 16 with ISR (incremental static regeneration), which fronts every store with a sub-500 ms cold-page target and millisecond-range warm pages. Traefik terminates SSL at the platform edge with Cloudflare for SaaS handling custom-domain SSL provisioning. The .NET 10 API is the dynamic origin for cart, checkout, and storefront APIs. Static page chrome (theme, navigation, hero, product grids on category pages) is cached and revalidated against Scribe and Loom API events, so no shopper ever waits for a cold database round-trip on a chrome render.

05Can I import from WordPress or Shopify?

WordPress + WooCommerce, Shopify, OpenCart, and osCommerce / ZenCart are the four migration paths in the platform roadmap (Phase 6.2 and 6.3). The Loom team has identified these as the dominant migration sources for Bangladeshi sellers and is treating one-click importers as a launch-gating capability. Pages get translated to Studio Section / Row / Column trees, products are mapped against the supplier catalog where matches exist, and order history imports as historical-only records that the trust score does not double-count.

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. Storefronts resolve to a tenant by custom domain (Cloudflare proxy mode through Traefik to the Storefront app) or by subdomain pattern slug.loom.bd. Studio, Admin, Scribe Admin, and the Platform console all run on the same RLS-guarded core, so an operator cannot accidentally read another tenant's pages or orders.