Built on · Vera
Vera — one admin for everything
Vera runs every website and e-shop we build: pages, products and orders in one admin, and a higher class just switches modules on. In production since 1 August 2026.
Vera in production since 1 Aug 2026
The mark
The same grid of four tiles as the LUMA mark, with one difference: the fourth tile is only an outline. Vera is where content is still being added, and the empty square waits for what you put into your site.
What is Vera?
Vera is the system LUMA Creative builds every website and every e-shop on. Instead of a stack of plugins that can stop understanding each other after any update, you get one admin for pages, products and orders. Two things follow from that in practice. A website that began as a presentation can start selling without being rebuilt. And when something needs fixing or adding, it happens inside one system, with one supplier, rather than two who pass the blame between them. Every class runs on Vera, and they differ only in how much of it is switched on.
Platform
Clients and channels grow.
Systems do not.
The catalogue from Vera goes through Prizma to the marketplaces, Iris runs sales and Sigma connects the ERP. Click any part of the diagram.
ERP
Your accounting system
SAP S/4HANA or SuperFaktúra. Master data, orders and invoices that somebody retypes by hand today.
Sigma
Vera ⇄ ERP integration draft 1.0
Connects the ERP with everything else. When a client is added, the connector changes, not the website.
Vera
CMS and e-shop in production since 1 Aug 2026
Content, catalogue, orders and invoices in one place. The single source of truth for the website and the shop.
Prizma
Channel manager live from 1 Nov 2026
The catalogue goes from Vera to marketplaces and comparison sites, orders come back. One stock for every channel.
Channels
Marketplaces and comparison sites
Allegro, Kaufland, Alza, eBay, Amazon and more. They are connected one at a time, so you can see what each channel really brings.
Iris
Console and telemetry working prototype
Runs sales on top of Prizma: a sales policy for each client, an operations overview, billing and audit.
01 · Vera
What Vera does
-
Everything in one place
Pages, articles, products and orders all live in one interface. No e-shop bolted onto the website as a second system, and no two logins to guess between when something needs changing.
-
You edit the content yourself
Text, photos and prices you change yourself, without waiting for a free slot in our calendar. A routine edit takes about a minute and needs nobody who can write code.
-
Moving up is a switch, not a rebuild
Iskra and Spektrum are not two different systems. A higher class means switching more modules on in the running site, so your content, your addresses and your search rankings stay exactly where they are.
-
Operations in a single payment
Hosting on our servers, off-server backups, uptime monitoring, updates to Vera and the SSL certificate with its renewals all belong to one monthly line item. None of it is billed separately on top.
-
Forms that really deliver
An enquiry goes out through a verified mail server and is stored in the admin at the same moment. Even if the message lands in spam or someone deletes it by accident, you still have the customer.
-
Speed built in, not bolted on
Images are recalculated into the lighter WebP format, finished pages are pre-generated and the target is a load under two seconds, phones included. Speed does not come from tuning at the end. It comes from the way the site is put together.
02 · Vera
What the admin looks like
Six screens, three of which you will open every day. The rest keeps out of your way until you need it.
-
Pages and articles
Add a page, write the text, drop in photos and publish. The menu, the breadcrumb trail and the sitemap for search engines fill themselves in, so nothing gets forgotten.
-
Products and stock
Price, stock, variants and photos on one screen. When stock reaches zero the product stops selling by itself, so you do not collect orders you have nothing to ship.
-
Orders
Each order shows its status, its payment, its delivery and the e-mails that went out to the customer. Nothing important lives only in your inbox.
-
Enquiries from forms
Everything sent from the site is stored and searchable. Six months on, you still know who asked what, and when.
-
Media
One place for photos and documents. Upload once, use it on several pages, and the sizes you need are worked out for you.
-
Users and rights
Your accountant can open the orders without being able to rewrite the homepage. Rights are set person by person, so everyone reaches exactly what they are responsible for.
03 · Vera
What runs in the background
You will see none of this on the site, and that is exactly the point. It runs for every class and it is part of the monthly operations fee.
-
Backups off the server
We back up daily, and somewhere other than the site itself. A backup on the same machine is not a backup, only a second copy of the same risk.
-
Uptime monitoring
If the site stops responding, monitoring is what tells us. We do not wait for your customer to notice and ring you on Monday morning.
-
Security updates
Updating Vera is our job. You never have to track what needs patching or hire somebody to watch it for you.
-
HTTPS and lawful cookies
The certificate renews itself, and the consent bar genuinely blocks what it says it blocks. A visitor and an inspector see the same thing.
Stack
What Vera runs on
Instead of a line about modern technology, here are the versions you can check for yourself. We stay on long-term support releases, the ones that will still be getting security patches in two years, rather than whatever shipped last week.
-
Node.js 24 LTS
The server runtime. The long-term support line rather than the newest one, because in production a fixed bug is worth more than a new feature.
-
Payload CMS 3
The content admin. Pages, products and orders in a single interface, with rights set person by person.
-
Express 5
The layer that serves requests from visitors. Templates render at request time, so there is no build step to break during a deploy.
-
MongoDB 8
The database for content and orders. Backed up daily, and away from the server it runs on.
-
Redis 8
The cache in front of the database. A page that has not changed is not recomputed, so the site keeps its pace when visitors arrive all at once.
-
Docker
Deployment. A new version ships as one complete image, so no state builds up on the server that nobody could reproduce.
Moving up a class, in practice
A site built as Iskra does not need rebuilding to start selling as Lúč. The modules for the catalogue, the cart and payments are switched on in the running site and the addresses stay the same, so search rankings and links from other sites keep working. The content you wrote stays where it was. You pay the difference between the classes plus the work on the new part, not for a second website. The pricing page shows what each class contains and what it costs.
Vera and Prizma
Once your e-shop runs on Vera, the next sales channel no longer has to be built from scratch. Prizma sends the catalogue from Vera out to marketplaces, while stock, prices and orders stay where you are used to finding them. One stock, several places to sell. If the numbers interest you first, open the pricing page.
