Websites and software for businesses

A business website, a first application release or an improvement to an existing system. We start with your business need and choose the engineering approach to match.

Where do we start?

Choose a starting point. Scope, responsibilities and an estimate are agreed before implementation.

A business website

A new website or redesign that helps customers find your services and get in touch.

Delivery scope
Agreed page structure, mobile layouts, technical SEO setup and launch.
What to bring
Your current URL, required pages and available copy and images.

A first application release

A focused web application, customer portal or internal tool built around one important workflow.

Delivery scope
Specification, agreed screens and integrations, testing and deployment.
What to bring
Users, the main task to solve, existing systems and target timeline.

Fix an existing system

Help with a slow application, unreliable integration or infrastructure problem.

Delivery scope
An environment review and proposed fix; implementation scoped against the findings.
What to bring
Problem description, reproduction steps and environment details. Do not send passwords through the form.
All services and technical capabilities →

Launch is not the end of the work

Agree who looks after the environment after launch. Hosting and maintenance can cover a website, an application or a server on your own provider account.

Build

A website, application or integration with an agreed scope.

Deploy

Environment setup, launch and any required migration.

Maintain

Updates, monitoring, backups and support under a separate agreement.

Explore managed hosting and maintenance

Product Engineering

Turn an idea or business requirement into a working product. Architecture, specification, prototyping, implementation, deployment and documentation belong to the same delivery.

  • SaaS applications and customer portals
  • Internal platforms and operational dashboards
  • Marketplaces and commerce systems
  • Technical product interfaces
Explore this area →

Runtime & Systems Engineering

When normal application development is not enough, we can go deeper. Build lower-level components where performance, control, portability or integration requires it.

  • Rust, C, C++ and WebAssembly
  • Browser runtimes and rendering engines
  • Android native components, Kotlin and JNI
  • CLI tools, daemons and protocol integrations
Explore this area →

Edge & Distributed Systems

Design event-driven systems across local, edge and server environments. Define where execution happens, who owns state and how components recover when connections fail.

  • Cloudflare Workers and Durable Objects
  • WebSockets and realtime communication
  • Queues, KV and object storage
  • Caching, synchronisation and background processing
Explore this area →

Developer Tools & Automation

Make complex technical work repeatable, observable and verifiable. Build tools around real workflows, from deployment and recovery to browser observation and runtime diagnostics.

  • CLI applications and release tooling
  • Backup, restore, migration and staging
  • Browser automation and validation
  • CI/CD, workflows and infrastructure automation
Explore this area →

AI & Document Systems

AI integrated into real software systems, not an isolated feature. Combine deterministic processing with retrieval and generation while keeping outputs inspectable and testable.

  • Document intelligence and structured content
  • Semantic search, embeddings and retrieval
  • PDF, presentation and web document workflows
  • Local/private AI and enrichment pipelines
Explore this area →

Web, Commerce & Content Platforms

High-performance websites and product platforms backed by maintainable engineering. Connect the user experience to content, authentication, payments and the systems behind the product.

  • React, Next.js and TypeScript
  • Headless CMS, Sanity and content platforms
  • Shopify integrations and WordPress
  • APIs, payments, multilingual products and SEO architecture
Explore this area →

Infrastructure & Security Engineering

Production reliability is part of the product. Design secure environments with observability and recovery built in, rather than treating operations as an afterthought.

  • Linux, containers and virtualization
  • Private/public cloud and secure networking
  • Application hardening and access control
  • Monitoring, logging, backup and recovery
Explore this area →

Before you decide

Before work starts, know what you are buying, how it is priced and who will maintain the result.

How are scope and pricing agreed?

Describe the goal, current situation and main problem to solve. Before implementation, we agree in writing on scope, acceptance criteria, pricing and responsibilities. If an estimate requires technical discovery, its scope and any fee are agreed first. External service costs and later development are separated in the proposal.

When can work start and when will it be ready?

The start date and target schedule are confirmed with the proposal. Scope, available content, system access and customer approvals affect timing. If requirements change, we agree on the impact on cost and schedule before additional work starts.

What is handed over and who owns the result?

The proposal defines deliverables, source code and usage rights, documentation and any training. Control of domains, service accounts and data is agreed explicitly. Third-party software remains subject to its own licence terms rather than a blanket ownership promise.

What happens after launch?

Before launch, we agree who handles updates, backups, monitoring and incidents. Delivery defects, further development and ongoing maintenance are distinguished in the agreement. Maintenance, service levels and on-call support are not automatically included in implementation.

Have a difficult software problem?

Whether you need a complete product, a custom runtime, an automation system or help with a technical bottleneck, tell us what you are trying to build.

Discuss a Project →