What the Hub connects
Bookings and calendar
Slots, events, registrations: entered once, visible on the site.
Orders and payments
Online payment with Stripe or SumUp, confirmation sent automatically.
Clients and members
A private area, with sign-in by a code received by e-mail.
Publications
News published on the site and on your networks at once.
Newsletters
Your subscribers connected to a tool such as Mailchimp, no exports.
Dashboards
The figures that matter, up to date, no spreadsheet to consolidate.
Restricted rights, per person
Management
See everything, decide everything, manage access and payment keys.
Administrator
Content, users, orders and refunds.
Editor
Text and images, with draft and preview, nothing else.
Business role
Front desk, cellar, registrations: only their own screen.
Every action is written to the log, mine included. You know who did what, and when.
How I build it
I listen to the real work
What your teams do, in what order, what slows them down.
I speak your language
Your categories, your statuses, your documents, not those of generic software.
I connect what exists
We keep the tools that do their job well, and connect them.
I run it
Go-live, short training, changes as your business evolves.
Faster integrations with MCP
MCP (Model Context Protocol) is an open standard that lets an AI assistant, such as Claude, read and act in your tools. Many vendors already publish their own: Stripe, Notion, GitHub, Atlassian.
Where a connector used to be developed, we plug in, set the rights, and test.
Plug in rather than build
When a tool has its own MCP server, the integration starts there: less code to write and maintain.
Your in-house tools too
For an internal tool, I write the MCP server that exposes it, with the same safeguards.
Limited rights
The assistant only reaches what you open: read-only by default, write access where it helps.
A person validates
Sensitive actions wait for approval, and every action is written to the log.
AI in its place
AI prepares: an e-mail classified, an answer proposed, a document summarised. A person decides.
Frequently asked questions
Is it a CRM?
Not in the sense of software you adapt to. It is the way you work turned into software: it can manage contacts, but it starts from your business.
Who sees what?
Each person has a role. An editor does not see payments, a business role only sees its own screen. Management handles access.
Who owns the site and the data?
You do. The content can be exported, the site is hosted with the provider of your choice, and your data trains no public model.
Do my tools have an MCP server?
Often, for off-the-shelf tools: we check together in the first conversation. If not, we go through their API, or I write the MCP server.
Is Lumineth Hub ready?
It is in beta: I use it for my own sites first, before opening it more widely.
How much does it cost?
Quoted after a first conversation. Set-up and running costs are stated up front, separately.
A tool that overflows, a process to simplify?
Reply within 24 business hours, no obligation.