LLeddra
Built for traditional wellness teams in Southeast Asia

From a booking request to a completed service—without another paper handoff.

Leddra gives customers, managers, therapists, and owners one fast workflow. Start with the front door today; build the trustworthy operating record underneath it over time.

LeddraPilot foundation

One booking record

Website and staff-created requests enter the same queue.

One resource plan

Therapist and room assignments stay attached to the visit.

One completion event

The owner sees what happened, not just what was scheduled.

Pilot scope

A closed operational loop, deliberately small

This foundation secures four role-specific surfaces and the shared data contract. Each product surface can now be built independently without inventing identity, permissions, or tenant boundaries again.

1 · Request

Customer submits a mobile-friendly booking request.

2 · Confirm

Manager checks time, therapist, and room before confirming.

3 · Serve

Therapist starts and completes only assigned services.

4 · See

Owner reviews daily flow and exceptions across branches.

Four surfaces, one source of truth

Customer · H5
Phone login, booking request, status, and future reminders.
Manager · Web
Booking queue, daily schedule, resource assignment, and arrival.
Therapist · H5
Only their schedule, service start, and completion.
Owner · Web + H5
Cross-branch operations, exceptions, and permission-controlled access.

Foundation decisions

Fast to enter. Hard to bypass.

Mature identity and authorization

Better Auth manages sessions; Casbin enforces role and branch permissions on every protected request.

Portable PostgreSQL data

Local Postgres today, hosted Postgres later—without tying the product to one proprietary database.

English + three local languages

English is the fallback, with Simplified Chinese, Vietnamese, and Thai built into the route structure.

Roadmap · not included in this pilot

The operational record becomes the foundation for a ledger.

We are not pretending the financial layer is finished. The current service-completion event is designed to become its reliable source when merchants prove the need.

Customer asset ledger

Stored value, bonus value, packages, adjustments, approvals, and full exports.

Commission reconciliation

Expected commissions from completed services, confirmed before payroll.

Regulated account integrations

Potential bank and safeguarded-account workflows only after legal, compliance, and partner validation.

More acquisition channels

Google booking entry, SMS/WhatsApp providers, and merchant-site embeds through adapters.

These are product directions, not current capabilities or regulatory claims.

First prove that one real store will run the loop.

The next milestone is not a bigger feature list. It is a shadow-mode pilot that shows less coordination work and a cleaner daily record.

Enter the pilot