In development · Marketplace

Chillum Casa

A marketplace for independent chillum makers and collectors—combining a considered editorial identity with accounts, catalogue workflows, moderation and commerce infrastructure.

Next.jsTypeScriptCloudflare WorkersD1R2
Chillum Casa mark
01 / The brief

A home for
the craft.

The challenge was not simply to put products online. It was to create a credible digital home where singular handmade pieces, their makers and the mechanics of a marketplace could coexist.

Make the marketplace feel like a collection—not a catalogue template.

Chillum Casa connects independent artisans with collectors while preserving the identity and provenance of each piece.

OMLAYER shaped the product from brand-facing experience through to authentication, maker workflows, catalogue management, image infrastructure and founder moderation.

02 / Product scope

Two sides.
One Casa.

Public discovery and private maker operations run on the same underlying product model.

01

Artisan profiles

Independent makers can present their practice, location and work as a coherent studio presence.

02

Piece catalogue

Structured listings support artistic titles, piece types, materials, pricing and multiple photographs.

03

Accounts & roles

Founder, artisan and customer paths separate permissions without fragmenting the experience.

04

Review workflow

Draft, pending review, changes requested and approval states give publishing a deliberate process.

05

Media pipeline

Originals and optimized variants live in R2, with galleries, cover selection and responsive presentation.

06

Marketplace foundation

Inventory, saved pieces and order infrastructure establish the base for commerce as the collection grows.

03 / System design

Editorial outside.
Systems inside.

The visible experience stays restrained while the operational layers handle identity, content, media and marketplace state.

Craft in front.
Infrastructure behind.

A Cloudflare-native architecture keeps the product compact: the application and Worker layer orchestrate workflows, D1 holds structured marketplace data, and R2 stores the original and optimized imagery that gives every piece its presence.

Marketplace interfaceCollection · Makers · Accounts
Next.js
Application layerAuth · Roles · Moderation · Catalogue
Worker
Structured dataProfiles · Listings · Products · Orders
D1
Media layerOriginals · Card variants · Detail variants
R2
04 / What mattered

Built to
grow carefully.

The platform is approaching launch. The architecture is intentionally additive so real makers and real inventory can shape what comes next.

A small marketplace still deserves real product architecture.

Existing listings remain compatible as the schema evolves. Image associations, moderation history and product metadata were introduced without destructive rewrites.

The result is a foundation that can move from a curated first collection toward a broader maker marketplace without replacing the core system.

Building a marketplace? We can design the layers behind it.

From the public experience to accounts, data, media and operational workflows, OMLAYER builds the product as one connected system.