[{"data":1,"prerenderedAt":170},["ShallowReactive",2],{"page-content:\u002Fen\u002Fservices":3},{"id":4,"title":5,"body":6,"description":13,"extension":14,"meta":15,"navigation":165,"path":166,"seo":167,"stem":168,"__hash__":169},"pages\u002Fen\u002Fservices.md","Magento development, consultancy, hosting and AI",{"type":7,"value":8,"toc":9},"minimark",[],{"title":10,"searchDepth":11,"depth":11,"links":12},"",2,[],"Magento development, e-commerce consultancy, Magento hosting and AI agents in your development process. One platform, known inside out. New builds, replatforms, Hyvä frontends and dedicated hosting.","md",{"hero":16,"development":34,"consultancy":64,"hosting":93,"ai":119,"notDoing":151,"closing":161},{"eyebrow":17,"headingLead":18,"headingAccent":19,"headingTail":10,"lede":20,"jump":21},"SERVICES","One platform,","known inside out.","We do four things, and they fit together: we build your Magento store, we work out where it can do better, we run it on infrastructure we manage ourselves, and we put AI agents into the work, our own and your team's. No hardware, no printers, no office networks.",[22,25,28,31],{"href":23,"label":24},"dev","01 Development",{"href":26,"label":27},"consult","02 Consultancy",{"href":29,"label":30},"hosting","03 Hosting",{"href":32,"label":33},"ai","04 AI",{"eyebrow":35,"heading":36,"paragraphs":37,"cta":40,"ctaPage":41,"cards":42,"panel":61},"01 · DEVELOPMENT","Magento development",[38,39],"New builds, replatforms and ongoing development on Magento 2 and Adobe Commerce. We write modules that survive an upgrade and leave no core hacks behind.","We prefer to build the frontend in Hyvä. Less JavaScript, faster pages, and a codebase the next developer can still follow.","Discuss your project →","contact",[43,46,49,52,55,58],{"title":44,"body":45},"New builds","From catalogue structure to checkout, delivered with documentation.",{"title":47,"body":48},"Replatform","From Magento 1, Shopware or custom to Magento 2, without a revenue gap.",{"title":50,"body":51},"Hyvä frontend","An existing store moved from Luma to Hyvä, usually in six to ten weeks.",{"title":53,"body":54},"Custom modules","Composer packages with tests, no changes in the core.",{"title":56,"body":57},"Integrations","ERP, PIM, WMS, feeds, search and payment providers. Asynchronous where it can be, with a cache layer where it has to be real-time, and never in a way that lets a slow ERP drag your store down with it.",{"title":59,"body":60},"Upgrades","Keeping up with releases and security patches without surprises.",{"label":62,"body":63},"HOW WE SHIP","Every pull request passes the same gates before it is merged: static analysis, tests and a review. Every release goes to staging first, with the same data and the same caching as production. Deploys are automated and can be rolled back within a minute.",{"eyebrow":65,"heading":66,"paragraphs":67,"cta":70,"ctaPage":71,"rows":72},"02 · CONSULTANCY","E-commerce consultancy",[68,69],"Your store runs, but revenue lags behind what the traffic promises. We find out where it leaks and put a number on it.","You get a priority list, not a presentation. Every item comes with its expected impact and an hours estimate, so you can decide for yourself what it is worth.","See the audit →","prijzen",[73,77,81,85,89],{"n":74,"title":75,"body":76},"01","Conversion research","Where visitors drop off, in which step, on which device, and what that costs per month in missed revenue.",{"n":78,"title":79,"body":80},"02","Checkout analysis","The most expensive part of your store. Shipping options, payment methods, error messages, load time per step.",{"n":82,"title":83,"body":84},"03","Catalogue & search","Filters, facets, relevance and speed. Visitors who find nothing buy nothing.",{"n":86,"title":87,"body":88},"04","Performance budget","A hard limit per page, agreed with you, enforced in the pipeline.",{"n":90,"title":91,"body":92},"05","Roadmap","What first, what later, what never. With hours and expected return per line.",{"eyebrow":94,"heading":95,"paragraphs":96,"cta":99,"ctaPage":71,"cards":100},"03 · HOSTING","Magento hosting",[97,98],"Magento is not an ordinary PHP application and it struggles on hosting set up to run everything at once. Our stack is tuned specifically for it.","Monitored from both sides: from outside for availability and response time, every five minutes from several locations, and from inside on the servers themselves. When something goes wrong, our phone rings, usually before you notice.","Plans and pricing →",[101,104,107,110,113,116],{"title":102,"body":103},"Varnish + Redis","Full page cache and sessions kept separate, tuned to your catalogue size.",{"title":105,"body":106},"Dedicated server","From the Start plan up, your store has the machine to itself. No neighbours on your CPU.",{"title":108,"body":109},"Staging = production","Optional on every plan: a separate server with the same configuration and data, so a test actually means something.",{"title":111,"body":112},"Backups","Automated, encrypted and kept off-site. And the restore has been tested, because a backup that was never restored is an assumption.",{"title":114,"body":115},"Security patches","Shortly after Adobe's release, through staging to production. If a hole is already being exploited, a mitigation goes live the same day, patch or no patch.",{"title":117,"body":118},"Monitoring 24\u002F7","The alert reaches us, not you. At night and at the weekend too.",{"eyebrow":120,"heading":121,"paragraphs":122,"cta":125,"ctaPage":126,"ctaAnchor":127,"rows":128,"panel":148},"04 · AI","AI in your development process",[123,124],"Everyone is talking about AI. We work with it, every day and for every client. Agents read through logs and code, review every pull request, investigate tickets before anyone starts on them and build on their own where they can. It makes us faster, and it makes the work cheaper for our clients.","What we use ourselves, we set up for your team as well. Not a chatbot beside the work, but agents inside your existing Jira, Git and CI pipeline, following the same coding rules as your developers, with limits enforced in code rather than left to good intentions.","How we use it →","cases","case-ai-werkwijze",[129,132,135,138,141,144],{"n":74,"title":130,"body":131},"Incident analysis","An agent reads slow logs, server metrics and application logs alongside the code. What used to take days of searching now often surfaces the cause within the hour: one query, one line of config.",{"n":78,"title":133,"body":134},"Code review","Every pull request reviewed against the project's own coding standards, with inline comments. Clean work moves on to test; a blocker goes back to the developer with an explanation.",{"n":82,"title":136,"body":137},"Ticket preparation and estimation","Before the team discusses a ticket, it has already been investigated in the real code: root cause, files, pitfalls, plus a reasoned story point estimate. Open questions have already gone to the right person.",{"n":86,"title":139,"body":140},"Autonomous development","A label on a ticket is enough: the agent creates the branch, writes the code, runs the checks and opens the pull requests. QA rejections get fixed on the same branch.",{"n":90,"title":142,"body":143},"Upgrades and takeovers","Modules compared against their originals, changelogs and patches read, dead code pointed out. Inherited codebases get mapped sooner, and upgrades go through faster.",{"n":145,"title":146,"body":147},"06","Guidelines and guardrails","One set of coding guidelines per repository that Claude, Copilot, Cursor and Junie all read, and hard limits on what an agent may push and merge. Fast, but never unsupervised.",{"label":149,"body":150},"HOW WE USE IT OURSELVES","Agents work for every client, from a store on a single server to an Adobe Commerce platform with three storefronts. On our largest development team, five routines run on their own every working day, from the morning prep to the release email. The first ticket built fully autonomously was ready within eleven minutes and passed QA and code review first time.",{"heading":152,"intro":153,"items":154},"What we do not do","Just as important. For these we know good people and are happy to point you to them.",[155,156,157,158,159,160],"On-site IT","Printers & hardware","Telephony","Office networks","Building on Shopify \u002F WooCommerce","Paid search campaigns",{"heading":162,"body":163,"cta":164},"Shall we take a look at your store?","Half an hour, screen shared, no sales pitch. You leave with three concrete improvements.","Book a call",true,"\u002Fen\u002Fservices",{"title":5,"description":13},"en\u002Fservices","HN6IEe-dSRXpARFaaYLKLuXvekv2JGrLw9L00y_iIdA",1791656283652]