A family of business tools, organised around the work people do every day
Kyloth brings five kinds of business work into one product family. A shop needs to handle orders; a customer team needs to follow up; a restaurant, clinic and school each have their own daily routines. Each Kyloth product has a distinct scope, so businesses can start with the one that fits their work.
| Product | Focus |
|---|---|
| Commerce | Products, orders, delivery, returns and repeat business. |
| Desk | Enquiries, customer relationships, quotes, support and follow-ups. |
| Table | Menus, stock, kitchen operations, service and bills. |
| Clinic | Bookings, queues, patient records, billing and follow-up care. |
| Class | Admissions, teaching, attendance, fees and school life. |
The repository brings the public website, theme discovery, merchant workflows and customer storefronts into a Next.js application. Bun and Turborepo manage the workspace, while shared database and configuration packages provide the foundation.
The server API is organised into tRPC routers for catalogue management, imports, onboarding, themes, store configuration, orders, checkout, customers, inventory, discounts and analytics. Zod validates inputs, and TanStack Query handles client-side data access. This keeps the interface connected to typed operations instead of duplicating request shapes across the browser and server.
Kyloth's theme system uses shared rendering components for gallery previews and published stores. A theme supplies its content, visual tokens and composition choices. Those choices include header structure, navigation, hero treatment and collection layout, so variation extends beyond changing colours.
Container queries let the renderer respond to the space it actually occupies. The same storefront can sit inside a small gallery preview or fill a browser window. That matters because a preview should demonstrate the product a merchant will publish, rather than a separate mock-up that gradually drifts from it.
Platform styles and storefront styles use separate CSS variable namespaces. A merchant's brand colour belongs to their shop; it should not change the dashboard around it. Cloudinary supplies responsive image delivery through a shared loader.
The database package separates administrative access from the lower-privilege connection used for tenant work. Its transaction wrapper sets the merchant identifier locally for each transaction. PostgreSQL row-level security policies use that scope to restrict access.
Making the scope transaction-local is an important detail with pooled connections: one merchant's context must not survive into another request. The repository includes database tests for cross-merchant access and policy coverage, alongside membership tests.
Commerce workflows bring together products, variants, inventory, discounts, delivery charges and payment-method rules. A correct calculation in isolation is only one part of the job. The amount shown to a customer must agree with the order the system records.
The Playwright checkout suite exercises that relationship by comparing the displayed purchase with the stored order, including its individual components. Targeted tests also cover stock, discounts, receipt tokens and concurrent checkout behaviour. These are examples of the repository's verification strategy, rather than claims about production transaction volume.
The public website lets visitors explore each product, compare its scope, and review website designs relevant to their business. Product pages distinguish what visitors can explore today from work still to come. Demonstration storefronts and catalogues are labelled as examples.
The product family also separates access from ownership of records: one login does not automatically grant access to every product or its data. Each product's permissions remain part of its own workflow.
This overview draws on the project repository and public website as reviewed on 22 October 2026. The architecture described above is grounded in the commerce implementation; it does not imply that every product in the family has identical capabilities. New sign-ups are not open yet; the live product pages provide the latest scope and availability.
Prabir Singh
Full-stack engineer from Mumbai. Twenty years in sales, now I build products that sell. More about me or start a project.
A browser-native BIM platform: heavy IFC building models converted on the server, so anyone can click a wall in the browser and read the exact engineering data behind it. No install, no plugin, no license.
A cybersecurity firm's whole web presence in one self-hosted Next.js codebase: marketing site, admin CMS, lead engine, and an AI chat desk