Features · Web apps
A member area, from a spec.
For clients, customers and members of your business.
A site plus a spec.
A web app is a website plus a spec: which kits it has, how the member area looks, who the members are and what custom entities it keeps. Your AI writes the spec or patches one of 22 starting points, and Geenius MVP checks it and names the JSON path of every problem before anything is saved.
- Members sign in by e-mail code or magic link, with sessions per device and lockout
- Custom entities with ten views
- Fictional sample data for a client portal
Kits
28 built, 4 not.
Members and records
Sign-in, the member shell and custom data.
Portal kits
Clients, matters, appointments, documents, invoices, messages and intake.
Service kits
Jobs, crew area, booking, stock, memberships, requests, reviews, loyalty and analytics.
Be clear about this
Cautions we repeat.
- Pre-betaRegion
The deployment runs in the United States. For law, health and tax starting points, use fictional data only until an EU region exists.
- Pre-betaLegal texts
They are templates, not legal advice. Have them checked.
- Pre-betaParts left in Geenius OS
Several portal kits read Geenius OS tools (Contacts, Matters, Bookings, Invoices, Files). They are not reached from the standalone app yet.
Questions
About web apps.
What is a web app here?
A website plus a spec: kits, the member area, members and your own entities. Members are the app's own people, such as clients or customers, and never Geenius OS accounts.
Which kits are there?
28 are built, among them members, records, portal, booking, jobs, crew, memberships, tickets, reviews, rewards and analytics. Four shop kits are not built yet: fulfilment, digital, customer accounts and returns.
Can I use it for client data?
The deployment runs in the United States. For law, health and tax starting points use fictional data only until an EU region exists. Legal texts are templates, not legal advice.