MIVABYTE

Back to services
Mivabyte service · Build

Websites & Web Apps

Custom websites and web apps, WordPress, or Shopware – we choose the technical foundation around the product, editorial workflow, and commerce needs.

Start a request
At a glance

Find the most important information directly.

Choose a section instead of reading the entire page linearly.

Optional service planning
Plan your build

Define what your website should become.

Answer a few focused questions and we’ll recommend the implementation path, supporting services, and how the project should be delivered.

Question 1

Are we starting new or working with something existing?
New projectThere is no existing website or application to preserve.
Existing websiteA website exists, but the current technology is not important or is unknown.
Existing WordPressKeep, rebuild, or extend a WordPress-based website.
Existing ShopwareWork with an existing Shopware store.
Existing custom applicationA custom website, portal, or web application already exists.
I’m not sureWe can infer the path from the requirements.

Question 2

What are we building?
Company website
Landing page
Portfolio / presentation site
Blog / magazine / content platform
Online shop
Customer portal
Web app / SaaS
Internal business tool
Something else

Question 3

What is the main business goal?
Generate leads / enquiries
Present the company or brand
Sell products or services
Publish and manage content
Let customers use a digital service
Give customers an account or portal
Support an internal workflow
Several of these

Question 4

Who should manage content after launch?
Almost nobodyContent changes will be rare.
I want to edit pages myself
Marketing / editorial team
Mostly developers
Not sure yet

Question 5

What functionality does it need?

Choose everything that applies.

Contact / lead forms
Blog / news
Search
Booking / appointments
User accounts
Customer dashboard
Payments
Subscriptions
Product catalogue
Checkout
File / document area
Custom workflows
Other custom functionality

Question 6

What kind of commerce does the project need?

Choose everything that matters. WordPress + WooCommerce is absolutely a valid commerce path when the shop does not need heavier commerce architecture.

Small / straightforward shopA manageable catalogue with standard buying flows.
Content-led website + shopMarketing/content is central and commerce is one part of the site.
Large product catalogue
Complex variants / product structures
B2B commerce
Customer-specific / complex pricing
ERP / PIM connected commerce
Subscription products
I’m not sure

Question 7

How much custom application logic is involved?
Mostly pages, content and forms
Some custom functionality
User-specific data and permissions
Complex workflows / processes
It is essentially a software product
I’m not sure

Question 8

Which external systems need to connect?

Choose all that matter.

None
CRM
ERP
PIM
Payment provider
Newsletter / marketing tools
Booking system
Existing API
Internal software
Something else

Question 9

What is the design situation?
Design is completely ready
Branding exists, website design does not
Use the existing website as a reference
We need a redesign
We need design + branding
Not sure yet

Question 10

What should happen to the existing system?
Keep it and extend it
Redesign it
Rebuild it
Migrate its content / data
Replace only parts of it
Analyse it first

Question 11

Do you have a preferred technical approach?

A preference influences the recommendation, but we will not force a platform when the requirements strongly point somewhere else.

Recommend the best approach
Custom development
WordPress / WooCommerce
Shopware
Headless setup
I don’t know

Question 12

How should the project be built?
Mivabyte builds everything for me
Build it together with me
I want to manage parts myself

Question 13

Do you already have hosting?
No
Yes, keep it
Yes, but migrate it
Yes, but Mivabyte should manage it
Not sure

Question 14

What should happen after launch?
Hand it over
Help when needed
Ongoing maintenance
Continuous development
Mivabyte handles everything technical

Explore service

Design & BrandingWebsite BuilderWebsites & Web AppsAI & AutomationWordPress DevelopmentHosting & AI HostingShopware & E-CommerceMaintenance, Optimization & MigrationsCustom Website / Web AppWordPress + WooCommerceShopware
Choose the closest answer. The recommendation can still combine several services when that makes more sense.

Websites & Web Apps

We plan and build digital products around the goal, content, user journeys, integrations, and long-term operation – custom or on the right platform.

Build

Three paths to the right digital product.

Not every project needs the same stack. We choose between custom development, WordPress, and Shopware based on what the product actually needs to do – and who will edit, extend, and operate it afterwards.

Choose the right build path

Technical paths

When the product does not fit a CMS-shaped box

Custom development is a strong fit for customer portals, platforms, SaaS products, internal tools, and websites with their own business logic. Interface, data model, roles, integrations, and deployment are planned as one product instead of being forced around the limits of a ready-made CMS.

Development workspace with code and a website preview
Custom development: interface, backend, and integrations as one controlled system.

Typical custom stack

Frontend

Next.js, React, and TypeScript for fast component-based interfaces and server-rendered websites.

Backend & data

Node.js, PostgreSQL, and when useful Redis, queues, or dedicated API layers around the product logic.

Open-source building blocks

Payload CMS, Strapi, Appwrite, or Supabase when auth, content, storage, admin, or realtime are already solved well.

Infrastructure

Docker, CI/CD, monitoring, backups, and reproducible deployments instead of hand-maintained server state.

We only build from scratch what is genuinely specific to the product. A proven open-source system can be part of the architecture while custom logic, UX, and integrations are built where they create actual product value.

What stays the same across every stack

Architecture, UX, responsive design, performance, accessibility, security, deployment, and long-term ownership are considered from the beginning. Design & Branding, Hosting & AI Hosting, and Maintenance, Optimization & Migrations can connect directly to the project.

Technical references engineered in-house

Product Advisor and Noomi are battle-tested in-house systems showing two distinct architectures: a Shopware plugin with AI search and a complete product across web, iOS, and Android.

Preconditions, limits, and effort

What to know before we start

What we need from you

A clear goal and the main user journeys, access to existing systems and content, and a person who can decide. For a relaunch, additionally access to the existing codebase.

Where the service ends

We plan and build the digital product. Ongoing editorial work, operation, model costs, and third-party services are included only when they are explicitly part of the project.

What changes the effort

The number of user roles and integrations, the scope of the data model and business logic, languages and accessibility requirements, the condition of an existing system, and whether a first release may deliberately stay small.

Common questions