Common questions

Neither, exactly. We start from a platform that already covers what most businesses share, and build the parts that are specific to you. The time goes into what makes you different, not into rewriting what everyone needs.

You do. Source code, design, content, domain, credentials and technical documentation are yours and are handed over on request, with no conditions attached.

Yes. Valenys works with clients across Europe and North America, and the platform runs in seven configured languages.

Laravel and MySQL on the server; Astro or Next.js for public front ends; Python for the accessibility scanning platform. Integrations cover the major payment processors, carriers, marketplaces and AI providers, and are confirmed per market during scoping.

With scoping, not with a number. We go through what you have, what it has to do, what it must connect to, and which constraints are legal rather than negotiable. The proposal that follows carries a fixed scope and a timeline. A price quoted before anyone has looked at your processes is a guess, and guesses are what make projects overrun.

Yes, and it is often the sensible order. Sales, commerce, content or accessibility can go first, with the rest added later against the same data. What we would not recommend is running two systems in parallel for a year — that is where the data drifts apart.

Yes. Products, customers, orders, invoices and content are imported, and the mapping is agreed during scoping — because the interesting part is never the export, it is what your fields mean.

Addresses are kept where they can be kept and redirected where they cannot, and the redirect map is part of the delivery, not an afterthought. The platform also reports broken links and missing redirects after launch, so a rank lost quietly gets noticed.

That is what the page builder is for. Pages are assembled from blocks — hero, text, features, steps, timeline, testimonials, team, clients, price tables, galleries, forms and more — reordered by dragging, with a live preview. Blocks can be scheduled to appear and disappear on a date, saved as reusable global sections or templates, and A/B tested one against another. Nothing about it requires touching code.

Either. We host and operate it if you want that, or it runs on your own infrastructure with your credentials. Both cases end the same way: the credentials are yours, and handed over on request.

Source code, data, design, content, domain, credentials and documentation are handed over without conditions. The cost of leaving is transition work, not a negotiation. We would rather write that down here than have it discovered later.

Yes, isolated from one another and administered together — which is the usual reason agencies and groups with several brands end up here.

Export and deletion on request, configurable retention, an audit log of who changed what, access keys scoped to a domain, and two-factor sign-in for administrators. Analytics on the public sites runs without cookies, which is why most of our sites do not need a consent wall for measurement.

They are rehearsed. Backups are verified by checksum and restored on a schedule against a separate database, because most organisations discover their backups do not restore on the day they need them. Copies are also pushed to any S3-compatible object store.

With an audit, because a budget for fixing without a measurement is a number someone invented. The audit gives a score, a list and a plan. The fixing itself happens in your code, done by your developers or by us as separate work. Then the statement and the conformance report document the state, including what is not fixed, and monitoring keeps the answer true after the next release.

The audit reports. It does not fix anything, and neither does the widget — that is worth saying plainly, because a good part of this market implies otherwise. What you get is a written report: which element fails, on which page, at which measured value, and what to change instead, with the language work drafted by AI and reviewed by a person before it goes into the report. The changes themselves are made in your code, by your own developers or by us under a separate engagement, quoted from the audit. Nothing we sell writes to your site.

Claude, Gemini and GPT are all supported, with automatic failover between them. A spending cap is checked before each call and a log is written even when a call fails, so the bill has an itemised explanation rather than a surprise.

Yes — through a REST API with scoped keys and webhooks to your other systems, which covers most CRM, ERP and accounting tools directly. Deeper integrations are quoted as implementation work, after we have seen what the other side actually exposes.

Support tickets with agreed service levels, a client portal, and monthly reporting. Maintenance is a contract, not a favour — which is the honest way to make sure someone is actually responsible.

Yes. There is a partner panel with cascading branding, so the platform and the accessibility widget run under your name, not ours.