Custom sites, commerce, SaaS, administration, backend, frontend, REST APIs, auth, inventory, workflow and migrations.
We design it.
We build it.
We operate it.
We build custom web products, business SaaS systems, commerce platforms, integrations and production infrastructure. Engineering, visual systems, operations and the ability to evolve remain under the same line of ownership.
We do not just build pages. We put business logic into operation.
Mobile-first frontend, Flask backend, PostgreSQL data models, permissions, APIs, payments and automated tests in one releasable system.
Fragmented data flow, manual status handling, permission workarounds and non-reproducible releases.
Architecture, data model, frontend, backend, API contract, migrations, permission model, tests, deployment package and documentation.
Systems need to exchange data, not merely exist beside one another.
Inventory master, catalog and stock synchronisation, payment and order lifecycles, idempotent REST operations, outbox, retries and observable failure handling.
- HMAC
- REST
- Idempotency
- Reservation lifecycle
- Stripe
- Outbox
- Retry
- Webhook
- Invoice integration
Vezoryx ↔ Tutto Marconi · product/catalog sync · inventory sync · reservation lifecycle · Stripe checkout
Deployment is not the end of the project. It is where production accountability begins.
Docker · AWS EC2 · Linux · Nginx · Gunicorn · PostgreSQL · GitHub Actions · self-hosted runner
Build
repository + lockfile
Test
automated test report
Image
versioned container
Deploy
migration + release
Health
public health contract
Operate
logs + backup + runbook
A visual system is not decoration. It is part of product usability.
Digital interfaces, brand application, print production, motion and web 3D are built from the same visual rules.
- Digital
- UI system · design tokens · responsive layout · component system · web assets
- Brand
- logo usage · colour system · typography · brand application
- DTP
- brochure · catalogue · business card · packaging · PDF/X · bleed · crop marks
- Motion / 3D
- DaVinci Resolve · Blender · animation · Three.js
Coding Bear Studio Neon Foundry · Vezoryx UI · Tutto commerce interface · Eva Miller brand and product experience
Not every system begins in the cloud.
Focused local networks and device setup for smaller business environments. This is separate from cloud DevOps and is not positioned as managed enterprise networking.
- Router
- DHCP
- Subnet
- Local network
- Synology NAS
- Permissions
- Server
- IP camera
- Remote support
- Documentation
Evidence from working systems.
Not testimonials or marketing metrics: the problem, solution and actual line of responsibility.

Vezoryx
- Problem
- Fragmented SME workflows and inventory data.
- Solution
- Multi-tenant SaaS with inventory, workflow and integration layers.
- Responsibility
- Product design, full-stack engineering, DevOps and operations.

Tutto Marconi
- Problem
- Connecting physical and online inventory, payment and orders.
- Solution
- Custom commerce runtime with Vezoryx inventory synchronisation.
- Responsibility
- Frontend, backend, payment/order lifecycle, integration and production.

Eva Miller
- Problem
- Online commerce aligned with an independent brand.
- Solution
- Custom commerce, order management and Barion payments.
- Responsibility
- Brand, backend, frontend, database and operations.

MyLuxHome
- Problem
- Stabilising an outdated legacy web system.
- Solution
- Layered Flask rebuild and cleaner production infrastructure.
- Responsibility
- Rebuild, migration and production stabilisation.
Three practical entry points.
New product
Relevant when
A new commerce platform, SaaS, business application or digital service.
First steps
Discovery · scope · architecture · prototype · release plan
Takeover and stabilisation
Relevant when
A failing system, missing tests, manual deployment or unpredictable production.
First steps
Repository · architecture · security · deployment audit
Continuous development and operations
Relevant when
A live production system needs features, integrations, monitoring or support.
What remains
Iterative releases, production support, measurable state and documented changes.
What remains after the project?
Not only a working page, but a versioned, testable and operable artifact system.
Local IT support, kept in a separate lane.
Networks, NAS, workstations and local device support for SMEs. It is intentionally separated from the primary product engineering offer.
Local IT details