Deibee — Modular Commerce Platform for Small Businesses

Since 2023, I've consistently worked with small businesses that needed custom software to support their operations: online stores, order management, internal workflows, and client-specific business rules.

While these businesses were small in size, their operational needs were often complex. However, building each system from scratch meant:

• Reimplementing the same core modules repeatedly
• Longer delivery times
• Increasing maintenance overhead across projects

I wanted a way to deliver powerful, custom systems to small businesses, without sacrificing architectural quality or development speed.

Most client projects shared a large set of common requirements:

• Products and catalogs
• Customers and user management
• Orders and payments
• Admin roles and permissions

At the same time, each business had critical domain-specific needs:

• A travel agency required passenger data, pickup details, and passport information per order
• A flower shop needed delivery scheduling, gift messages, and recipient metadata
• Other businesses introduced their own variations in both products and orders

Traditional approaches would lead to:

• Forked codebases
• Client-specific endpoints
• Tight coupling between business rules and core logic

This did not scale—neither technically nor operationally.

To solve this, I designed and built Deibee, a private SaaS-style platform that acts as a shared core for multiple client systems.

Key Concept

Deibee is not a public SaaS product. It is an internal, reusable platform that allows me to rapidly deliver custom systems while maintaining a single, well-structured core codebase.

Clients are unaware of the platform's existence—they simply receive a tailored system built for their business.

Backend

• Single core backend
• NestJS + PostgreSQL
• Centralized domain logic and infrastructure

Frontend

• One frontend per business
• Next.js
• Allows full customization per client without affecting the core platform

This architecture strikes a balance between centralization of generic functionality and flexibility for business-specific requirements.

The main architectural challenge was handling high variability in products and orders without fragmenting the system.

Orders & Products Design

Instead of creating one endpoint per business type or one data model per client, I designed:

• A single, generic order and product pipeline
• Extensible data structures
• Clear separation between core attributes and domain-specific extensions

Through careful use of design patterns, abstraction layers, and explicit domain boundaries, I enabled different businesses to:

• Create entirely different order types
• Use the same backend endpoints
• Share the same infrastructure and persistence layer

This significantly reduced duplication while preserving flexibility.

Development Speed

• New client systems can be delivered much faster
• Core functionality is already stable and battle-tested

Maintainability

• One core backend to evolve and improve
• Bug fixes and improvements benefit all projects

Scalability (Developer-wise)

• Enables handling multiple active clients without codebase sprawl
• Clear mental model across projects

Client Experience

• Each client receives a system tailored to their business
• No exposure to SaaS complexity or unnecessary abstractions

Deibee is intentionally not commercialized as a public SaaS.

Its primary goal is:

• To improve internal efficiency
• To enforce architectural consistency
• To support high-quality, custom software delivery

It is a long-term platform that I continue to evolve and refine as new business requirements emerge.

• Small businesses can greatly benefit from well-designed software platforms
• Reusability requires deliberate architecture, not shortcuts
• Generic systems must be extensible, not rigid
• A single-core / multiple-frontends model provides an excellent balance of control and flexibility
• Internal platforms can be just as complex—and valuable—as public SaaS products