This is the page where we explain why we exist. If you’re interested in what we sell, you’ll want to know who you’re dealing with. There’s no founder storytelling here, no generic ‘mission and values’ — the brand proves itself through what we do every day, not through a paragraph on an About page. But there are decisions we’ve made that are worth putting in writing so you know what to expect.
The problem with the current market
The plugin and module market for online stores has been inflated for years. Product pages promise ‘transform your store’, ‘the best X 2026’, ‘+50,000 customers trust us’. Five-star reviews that look too similar to each other. Retouched screenshots. Demo videos where everything loads instantly because they’re recorded in an empty sandbox. 7-day return policy in fine print. Technical support that replies with the same template email for a week before starting to address the actual problem.
Every one of those points is carefully measured by marketing. Every one works on a conversion dashboard. And every one leaves the customer with an odd feeling — the feeling of having bought something different from what they expected.
What happens next is predictable: you end up with a module that works for the demo case and almost nothing else, support that asks for credentials by email for days, an invoice that says €79 and a month later a silent renewal of €79 because the ‘lifetime’ had fine print in an FAQ you opened six months ago.
We’re not going to pretend the entire market is like this. There are serious people doing serious work. But the amount of marketing above product in this sector is high, and it’s what ended up tiring us out enough to do something different.
What we won’t do
- We don’t promise what we can’t deliver. Every product page includes a ‘When NOT to buy this module’ section. If your case fits those points, we tell you upfront to save your money.
- We don’t cripple the Free version. Free is the real module with a reasonable limit (X carts per month, Y FAQs per product, etc.). It’s not a locked screen with an ‘upgrade’ button. If it does what you need within that limit, you stay on Free with no extra steps.
- We don’t buy reviews or trade mentions. If someone writes about us, it’s because they bought something and it worked or it didn’t. Both kinds of feedback help us improve.
- We don’t use fake urgency. No flashing banners with ‘offer ends in 2 hours’. The price is the price.
- We don’t name-drop competitors. Other developers do their work and compete in the same market. If you want to compare Zeyvro against another option, we give you the technical specs and you compare.
- We don’t talk about ‘transforming your store’. We sell modules. They solve a specific problem. That’s it.
What we will do
- Public versioned changelog. Every release has a factual changelog with commit-level detail when applicable. If we add a feature we say so, if we fix a bug we say so, if we break compatibility we flag it in red at the top.
- No refunds once downloaded. Modules and plugins are digital products: once you access the file we can’t verify you haven’t used it, so we don’t apply refunds. Same logic as a downloaded PDF or song (Art. 103.m LGCU). If the module doesn’t work as documented, write to hola@zeyvro.com and we’ll fix it — that’s not a refund, that’s the product needing to work. See return policy.
- Ticket-based support, no chat or phone. We manage from a single inbox with a visible SLA (12–24 business hours). The person who replies is the one who wrote the module’s code, not a first-level support agent who escalates. If you have a specific technical question and go into detail, we reply in detail.
- Part of the catalog is open source. Some modules (like Cloudflare Turnstile or FAQ Accordion with JSON-LD) are published on GitHub under MIT license. The rest of the catalog isn’t, because we want the business to be sustainable, but we want you to know we can write the code we deliver.
- Public roadmap with dates and priorities. We say what we’re going to publish and when. If a date moves, we update and leave a trail. No vaporware modules on the list.
About this site
This site is built on WordPress + WooCommerce with the Astra theme. For a technical blog and a digital products store it was the cleanest tool: straightforward setup, mature plugin ecosystem, full database control, low operating costs, decent performance with cache properly configured.
If we were selling physical products with Spanish fiscal compliance (TicketBAI, VeriFactu, recargo de equivalencia), we would have gone with PrestaShop. Every platform has its sweet spot and this is WordPress’s.
We build modules for both because we know both deeply after years of running production stores on each. The tool serves the product, not the other way around. If at some point the context changes and another platform fits better for what we sell, we’ll say so upfront and migrate without telling you a story about ‘strategic evolution’.
The exact stack of active plugins is described in the post about the honest WooCommerce plugin stack. It’s a real use case: the site you’re reading. If you want to replicate part of the setup, the plugins, versions, and configurations we use are all there.
How you’ll notice it without us pointing it out
We’re not going to highlight the differences on every product page. Each decision described above proves itself through real experience, not through a banner. If you buy something, here’s what you’ll notice:
- The confirmation email arrives in seconds and includes the downloadable ZIP and license key.
- The first support ticket gets a reply within 24 business hours and goes into technical detail.
- The changelog is updated with every release, with no vague messages like ‘various improvements’.
- Product pages have a ‘When NOT to buy’ section near the price.
- The price you see is the final price.
- If the module doesn’t work as documented, we fix it. What there isn’t is a refund for a change of mind: it’s a downloaded digital product (Art. 103.m).
A legal note: for digital products, once you initiate the download the right of withdrawal does not apply (Art. 103.m of Royal Legislative Decree 1/2007). That’s why we don’t issue refunds on downloaded modules. What we do guarantee: if the module doesn’t work as its documentation describes, write to hola@zeyvro.com and we’ll resolve it — that’s not a return, that’s the product needing to work.
If on any of the above points you find the opposite, write to admin@zeyvro.com.
Visible roadmap
We have a public roadmap of 22 modules through Q2 2027. It’s organized by quarter with estimated dates, priorities, and the reasoning behind each decision. We’ll publish quarterly updates here on the blog and maintain a roadmap page updated with each item’s status. If there’s a module that doesn’t appear and you need it, write to us — real market gaps are what interests us most to fill.
If you’ve read this far, thank you. The brand proves itself over time: with every release, every closed ticket, every published changelog. This page exists so that in six months you can compare what we say today with what we’re doing then. No sugarcoating.
If you want to follow the project, subscribe to the monthly newsletter with catalog updates and blog posts. No spam, no tricks — the same standard we apply to everything else.