Built on · Vera
Vera one admin
Vera is the system behind every website and e-shop we build. One admin for pages, products and orders. Moving up a class means switching modules on, not starting over.
The mark
A prism on the left, three bars on the right. One beam goes in and three levels of equipment come out: the same system, fitted differently. The bars get shorter, they never disappear. A lower class is not a different product, it simply has less switched on.
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. That means two things in practice. A website that started out as a presentation can begin selling without being rebuilt. And when something needs fixing or adding, it happens inside one system, with one supplier. Every class runs on Vera. They differ only in how much of it is switched on.
What Vera does
-
One admin, not three
Pages, articles, products and orders all sit in one place. No e-shop bolted onto the website as a second system, no two logins and no two different ideas of where things get changed.
-
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 a two-hour admin training can be ordered on top.
-
Moving up a class is switching on
Iskra and Spektrum are not two different systems. Moving up means switching modules on in the running site, so your content, your addresses and your search rankings all stay where they are.
-
Operations in a single payment
Off-server backups, uptime monitoring, security updates and the SSL certificate with its renewals all belong to the monthly operations fee. Nothing is billed item by item on top of it.
-
Forms that actually deliver
An enquiry goes out through a verified mail server and is stored in the admin at the same time. If the message lands in spam or someone deletes it by accident, you still have the enquiry.
-
Speed as part of the build
Images are converted to WebP, pages are pre-generated and the target is a load under two seconds even on a phone. Speed is not something tuned at the end. It comes from the way the site is built.
What the admin looks like
Six screens, three of which you will use every day. The rest stays 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 breadcrumbs and the sitemap update themselves, so nothing gets forgotten.
-
Products and stock
Price, stock, variants and photos on a single screen. When stock hits zero, the product stops selling by itself instead of collecting orders you cannot ship.
-
Orders
Every order with its status, payment, delivery and the e-mails the customer received. Nothing important lives only in your inbox.
-
Enquiries from forms
Everything sent from the site is stored and searchable. Six months later you still know exactly who asked about what.
-
Media
One place for photos and documents. Upload once, use it on several pages, and the sizes you need are generated for you.
-
Users and rights
Your accountant can see the orders without being able to rewrite the homepage. Rights are set per person, so everyone reaches exactly what they are responsible for.
What runs in the background
You will never see any of this, and that is the point. It runs for every class and belongs to 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. Not your customer, and not on Monday morning.
-
Security updates
Updates to Vera are ours to run. You never have to track what needs patching or hire someone to watch it for you.
-
HTTPS and lawful cookies
The certificate renews itself and the consent banner really does block what it says it blocks. A visitor and an inspection see the same thing.
What Vera runs on
Not "modern technologies" but specific versions you can check for yourself. We stay on long-term support releases, the ones that will still get 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 freshest 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 per person.
-
Express 5
The layer that serves requests. Templates render at request time, so there is no build step that could break during a deploy.
-
MongoDB 8
The database for content and orders. Backed up daily and off 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 even under a burst of traffic.
-
Docker
Deployment. A new version ships as one whole image, so no state builds up on the server that nobody could reproduce.
Moving up a class, in practice
A site built as Iskra can start selling as Lúč without a rebuild. 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 exactly where it was. You pay the difference between the classes plus the work on the new part, not for the whole website a second time. What each class costs and contains is in the pricing list.
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 sales channels. If you would rather see the numbers first, open the pricing list.