Features
Everything a professional website calls for.
Seven areas, one tool, one database. Each has its own page, with a real configuration example.
Sections, rows, blocks. Twenty-four content types, and a different number of columns on desktop, tablet and mobile.
A template designed once, as many product pages as you have items. Cart, orders, stock, VAT.
You set your availability; the time slots follow from it. Automatic reminders, Google Calendar sync.
Answers that carry weights towards profiles, and a result page for each profile.
Modules, progress tracking, controlled access. Sold like any other product.
Sixty-seven transactional emails whose body is an ordinary page, in your own colours.
A token-based API so an agent can build the site. One role per area, each granted and revoked on its own.
Lists, a sign-up block, proof of every consent; newsletters composed like your pages, sent now or at the time you choose, and your subscribers in the CRM.
Claude on your site, from your phone
Add your site as a connector on claude.ai: Claude edits your pages whenever you ask, from your computer or the mobile app. Three steps, no code.
What works without any setup
These mechanisms have no settings page: they simply apply. They are as much a part of the product as everything else, and they account for much of what you gain by not stitching five services together.
Render caching
The body of every page is cached after it is first rendered, under a key that carries the page version — and, for a record page, the version of the record shown. Any change invalidates the key: there is nothing to purge by hand, and no risk of serving a stale page.
Built-in performance
Images generated in five sizes and served to match the actual width, CSS minified on publication, non-critical stylesheets loaded after first paint, fonts hosted on the site and shown without waiting. The PageSpeed score is measured automatically and can be checked page by page, failed audits included.
Structured data
Schema.org markup for product pages — name, SKU, price, availability, brand — is generated from the real data. Nothing is entered twice, so nothing can drift apart.
Backups and updates
The database and files are backed up daily. Updates are started from the admin panel: the package checksum is verified, then backup, migrations, restart — and the previous version is restored if any step fails.
Compliance
A cookie banner with time-stamped proof of consent, legal pages, data export and erasure on request, and a security log of sign-ins and role changes.
Multilingual
The admin panel is translated, and each account picks its own language, independently of the public site. The public site itself can run in several languages, one page per language, each at its own address.
Everything else, already there
What a serious site needs, and that you won't have to wire up.
Stripe in four fields, verified amounts, access granted on payment.
Customer area, two-factor authentication, GDPR export and erasure.
A page designed once, as many pages as records.
One version per language under /en/, without touching your addresses.
What JEIKO blocks by default, and why.
A cache that runs itself, images at the right size.
A ready, secured server in one command, that maintains itself.
The technical stack, and what it guarantees you.
Tutorial, configuration, module guides.
Every area has its own documentation
The pages above describe what JEIKO does. The documentation explains how to set it up, with examples.