Vedron is where the platform I built for Rinosbike becomes a product other businesses can run on. Small and mid-sized sellers get one system for their shops, their ERP and their marketplaces, set up around how they already work, with us staying on as the team behind it.

I’ve been on it since the start, working directly with the CEO. My part is product development and design: what we build, how it looks, how it fits together. I designed the distributed architecture behind the multi-service business, the CMS admin, the customer account and vedron.io itself. The code is written with Claude Code. I decide the architecture, review what comes out, and run it in production.

Screenshots

What’s in it

• VedronCMS: storefront and every page, edited without a developer. Multi-language, multi-country, built for search.
• VedronERP: orders from every channel, one stock number, invoices each country accepts.
• One customer account: sites, ERP, mailboxes and sign-in in one place, with a direct line to ask for changes.
• Agents for the repetitive work: multiple AI agents take over the daily chores, like answering customer mail in the customer’s language and an SEO agent that checks the sites every morning.
• Design system: one icon-only mark, a glass-and-pastel 3D visual language, and a full set of generated product graphics and blog covers that stay consistent across the site and the admin.
• Built on the same core as RinosCMS: tenant isolation at the database layer (PostgreSQL row-level security), storefronts at the edge on Cloudflare Workers.