Custom Software

Software built to be owned, not rented

Systems engineered for your processes, handed over with full code ownership, documentation and a team that can run them.

Off-the-shelf covers the common ground; the part that makes you different is where it forces compromises. We build that part as maintainable platforms: multi-tenant SaaS, internal systems, APIs and integrations, engineered to production standard from week one.

order.ts
src
core.ts
order.ts
api.ts
db.ts
class Order {
id: string
total: Money
validate() { … }
}
Domain modelCI-gatedYou own it

The call we usually get

A company runs its core process on spreadsheets, a legacy tool nobody dares to touch, or a SaaS product it has outgrown. Every workaround costs hours, every export is a risk, and the vendor roadmap does not care. They do not want an app. They want the process to run, auditable and fast, with software that belongs to them.

When custom software is the right call

Off-the-shelf covers the common ground. The part where your margin and differentiation live is exactly where standard tools force compromises and brittle workarounds. Custom software is the right call when a process is core to how you compete, when integration and data ownership matter, and when you need a system your team can change for years without licence ceilings. When a product already fits, we say so and help you configure it instead of building.

  • A workflow that is core to how you compete, not a commodity
  • Real integration with your ERP, PIM and internal systems
  • Full code and data ownership, no per-seat ceilings
  • A platform your team extends for years, not a black box

The system we build

Requirements & domain model
Architecture & APIs
Build & integrate
Automated tests & CI
Deploy to your cloud

From your domain to a system you own: designed, built, tested and shipped into your own cloud, with the code and the decisions documented.

Where teams put this to work

Concrete situations this is built for, across different teams and stages.

Mittelstand

A core process runs on a spreadsheet only one person fully understands.

We turn it into a system your whole team operates, with the business rules written down instead of living in one head.

B2B distribution

Orders, quotes and stock live in disconnected tools and nobody trusts the numbers.

We build one system that fits how you actually sell, syncing the tools you keep instead of replacing all of them at once.

Scale-ups

The MVP works, but every new customer makes it slower and more fragile.

We re-architect for scale and reliability in stages, without stopping the business to do it.

Enterprise IT

A legacy system still runs the business and nobody wants to touch it.

We modernize it slice by slice behind a stable interface, so nothing breaks while it changes.

Agencies

You won the project but lack the senior backend capacity to deliver it.

We deliver it as a bounded work package under NDA, invisible to your client and built under your brand, with the IP passing through you to the end client, so you keep the relationship and we carry the result.

Customer-facing

Your customers keep asking for a portal they can log into and serve themselves.

We build the portal and the integrations behind it, on your domain and your stack, so it stays yours.

Who this is for

Mittelstand and product teams

Mittelstand operations

You run the business on spreadsheets and one system nobody dares to touch. We replace the fragile core with a platform your people trust, handed over documented, so the knowledge does not walk out with one developer.

A documented handover, your code and your data, GDPR-grade, no key-person and no vendor lock-in.

Product and digital leads

You have a roadmap, but every feature fights the limits of an off-the-shelf tool. We build the part that is genuinely yours to shape, so your roadmap stops being a negotiation with a vendor's release schedule.

The custom core is yours to shape, so you own the roadmap and the source, not a vendor's release calendar.

CTOs scaling the platform

The MVP got you here; it will not get you to the next order of magnitude. We re-architect for scale and reliability without a big-bang rewrite that stops the business while it happens.

Incremental re-architecture by senior engineers, EU-hosted, with the system fully in your hands.

Scope the pilot

Founders and procurement

Founders and scale-ups

Speed matters more than polish, but throwaway code becomes next year's tax. We move fast on a foundation that does not need rebuilding at the next funding round.

A fast, senior build in a 90-day pilot on a foundation you own and can scale, not throwaway code.

Scope the pilot

Procurement and IT governance

You need to know who owns the code, where the data sits, and what happens if the supplier disappears. We can answer each of these, and put it in writing.

Full source handover, data residency in your jurisdiction, EU or your own region, AVV and TOM readiness, and clear exit terms in writing.

Request a quote

How we engineer it

Production discipline from the first commit, not bolted on after launch.

Domain-driven design

A model that mirrors your business, so the code stays legible as the system grows.

Type-safe end to end

TypeScript and typed contracts from database to UI, so refactors stay fast and safe.

Tested and CI-gated

Automated tests and pipelines that block regressions before they reach production.

Documented decisions

Architecture decision records and runbooks, so the system survives any single person.

Observable in production

Metrics, logs and traces wired in from day one, not added after an incident.

Yours to own

Your repositories, your infrastructure, your IP, handed over with full documentation.

What we build

Business platforms

The systems your operation runs on: order management, planning, approval workflows, customer portals.

  • Process modeling before code
  • Role and permission models that match reality
  • Audit trails as a feature, not an afterthought

Multi-tenant SaaS

From single-client build to product: isolation, billing, onboarding and the operations tooling behind it.

  • Tenant isolation as architecture
  • Usage and cost transparency per tenant
  • Migrations engineered for the tenth tenant

APIs and integrations

The connective tissue between ERP, CRM, shop and the tools your teams already use.

  • Idempotent by design
  • Dead-letter queues and alerting
  • Versioned contracts your partners can rely on

Legacy modernization

Strangler-pattern migrations that replace systems piece by piece while the business keeps running.

  • Old path alive until the new one is proven
  • Data migrations with dry runs
  • No big-bang weekends

How this fits your stack

The same idea wears a different shape per engagement. Pick how you would work with us and see exactly where the boundaries sit.

ERP & suppliers
PIM: enrich & validate
Shop, marketplace, print

One trusted product record flows from your ERP and suppliers, gets enriched and validated once, then ships to every channel that needs it.

How a build runs

The 90-Day Production Pilot is the default frame: one scoped system, production-grade, in your infrastructure. Larger programs are sequenced as pilots that compound.

How we build it

  1. 1Scoping week: process mapping, architecture decision records, a fixed scope you sign off
  2. 2Weekly shippable slices into a deployed environment you can click from week one
  3. 3Hardening and handover: documentation, runbook, your team operating the system

What you get

  • Source code in your repositories from day one, ownership contractual
  • Architecture documentation and decision records your next hire can read
  • A runbook and a team that has operated the system together with us
Loading diagram...

Reference architecture: Users / Clients, Gateway + Auth, Domain services, Database, ERP / CRM integrations, Audit log

How we work

From the first call to a system running in production, and supported after.

    01

    Discovery and planning

    We map the process, the constraints and the people who use it, then agree the scope and the shape of the system before any code is written.

    02

    Architecture and design

    We design the domain model, the data and the interfaces, and write the decisions down so the system stays understandable as it grows.

    03

    Build, reviewed and tested

    We build in small, reviewed increments, type-safe and covered by tests that run on every change, so regressions are caught before you see them.

    04

    Infrastructure and release

    We deploy into your cloud and your accounts through an automated pipeline, with releases you can repeat and roll back without drama.

    05

    Observe and monitor

    We ship logging, metrics and alerts from day one, so we see problems early, often before your users report them.

    06

    Support and iterate

    After launch we fix, extend and harden on a cadence that fits you, with full handover so you are never dependent on us to keep running.

How we run the engagement

Agile sprints

When scope will evolve: we ship in short increments and you steer priorities as the product takes shape.

Fixed work package

When scope is defined and you need a firm price: a contract with result responsibility and a fixed deliverable.

Ongoing partnership

When the system is live and growing: a retainer for changes, support and new features, on notice you control.

White-label work package

When you sell delivery under your own brand: we work under NDA, in your repositories and tooling, hand the IP through to your end client, stay off your client communication unless you bring us in under your lead, and sign off against acceptance criteria written before the build.

From commit to running in your cloud

A single delivery path you can read end to end: every change moves through the same gates, and the same path runs in reverse when something needs to be pulled back.

Commit
CI gates
Artifact
Staging
Production
Observability
Staging, Production and Observability run in your cloud accounts
Rollback path:ObservabilityArtifact or Production

Where uptime matters, we agree it as an SLA target, not a measured promise.

Build, configure, or buy?

Custom is not always the answer. Here is where each option wins, so you spend on the right one.

Scroll to compare

Off-the-shelf productConfigure a platformCustom build
Fits a process unique to how you compete
Fastest to get started
Lowest upfront cost
Deep integration with your ERP, PIM and tools
You own the code and data
No per-seat or revenue licence ceiling
Your team can change it for years

When a product already fits, we will tell you and help you configure it instead of building.

Why Oronts

Why teams build it with us

We are not the biggest shop you can hire. Here is why owners pick us anyway.

You own everything

The code, the data and the IP are yours, transferred on delivery. No lock-in, no per-seat ceiling, no vendor you cannot leave.

Senior and founder-led

The people who scope your system build it. Senior engineering throughout, no junior hand-off after the pitch.

AI-native, fast without cutting corners

A small senior team with an AI-assisted workflow moves quickly and keeps the codebase clean, typed and tested.

A fixed-price way to start

Our 90-day production pilot puts a first usable slice into a fixed scope and price, so you judge us on shipped software before committing further.

verify
$npm test && npm run build|
test suites passed
type check: clean
build complete

The stack we build on

Built for procurement

The answers a buying committee checks, before you have to ask.

Code ownership
Your repositories and IP, transferred on delivery under a work-for-hire agreement.
Hosting
Your cloud, your region, your tenancy. We deploy into your accounts, not ours.
Data
Customer data stays in the infrastructure we agree on, and we do not use it to train models.
Documentation
Architecture decision records, runbooks and a handover your team can act on.
Support
An optional retainer after launch. You are never locked into it to keep running.
Continuity
Full ownership and documentation mean any senior team can continue the work.
Data processing
An AVV per Art. 28 GDPR with a TOM document, ready to sign before we touch production data.
Subprocessors
A documented subprocessor list; you approve any processor before it is used.
Security review
We complete your security questionnaire and provide the security evidence your procurement needs, such as insurance proof or a BSI CyberRisikoCheck attestation, where required.
Acceptance
Defined acceptance criteria per milestone, so sign-off is against a written standard, not opinion.

Who owns what

Whether you contract Oronts directly or work with us under a prime or MSP, every link in the delivery chain has one clear owner.

Responsibility ownership across the delivery chain
ResponsibilityOrontsPrime / MSPYouCloud / model provider
Build & result responsibilityOronts owns Build & result responsibility
Code & IP ownershipYou owns Code & IP ownership
Hosting & infrastructureYou owns Hosting & infrastructureCloud / model provider owns Hosting & infrastructure
Data processing (AVV / TOM)Oronts owns Data processing (AVV / TOM)You owns Data processing (AVV / TOM)
Security questionnaire / attestationOronts owns Security questionnaire / attestationPrime / MSP owns Security questionnaire / attestation
Acceptance sign-offYou owns Acceptance sign-off
Incident response (agreed SLA)Oronts owns Incident response (agreed SLA)Prime / MSP owns Incident response (agreed SLA)

When we are not the right choice

  • You need staff augmentation by the hour inside your own ticket queue; we deliver scoped work packages with result responsibility
  • An off-the-shelf product genuinely covers your process; we will say so in the first call
  • Budgets below the published bands; quality has a floor

Engagement levels

Oronts works with serious teams that need senior delivery, not low-cost outsourcing.

Production Pilot
from 25k EUR
Custom software and AI projects
from 50k EUR
Ongoing technical retainers
from 15k EUR/month

Exact pricing depends on scope, responsibility, delivery speed, team size, integrations, support expectations and production risk.

Frequently Asked Questions

Custom builds start from 25k EUR for a focused internal tool and from 50k EUR for a platform with integrations, payments and role-based access; the final figure depends on scope, the number of integrations and timeline. We give an itemized estimate after a short discovery workshop where we map your requirements, user flows and constraints, and the estimate breaks each feature into effort ranges so you can prioritize and phase the build to your budget. Where an off-the-shelf component does the job, we say so rather than build it from scratch.
Timelines depend on scope, the number of integrations and how much has to connect to existing systems, so we commit to a timeline against your agreed scope rather than a generic number. We work in two-week sprints and demo working software at the end of each one, so you steer with running software instead of slides and can course-correct as priorities change. For a bounded start, our 90-day production pilot frames a first usable slice into a fixed window and the full build is planned from there. We also plan time for testing, hardening and deployment before go-live, because shipping known issues costs more than a short delay.
Yes, we adapt to your existing infrastructure and team capabilities rather than forcing a rewrite. Our engineers work across React, Vue, Angular, Node.js, PHP (Laravel, Symfony), Python, Go, Rust, and Java, so we can integrate with most modern stacks. If your backend runs on Laravel and your team knows PHP well, we will build on that foundation instead of suggesting a migration to Node.js for the sake of novelty. We only recommend technology changes when there is a clear, measurable benefit that justifies the disruption. For instance, if your Python monolith struggles with real-time WebSocket connections, we might suggest adding a small Go service for that specific need rather than rewriting everything. In every case, we explain the trade-offs in terms of cost, timeline, and maintenance burden and let you make the final call. Our goal is to strengthen what you already have, not to introduce unnecessary complexity.
After launch, we offer ongoing support packages that cover monitoring, maintenance, security updates, and continued feature development. The first month post-launch typically involves closer attention: we watch error logs, performance metrics, and user feedback channels to catch issues early and deploy fixes quickly. After that initial stabilization, support transitions to a monthly retainer where you get a set number of development hours for new features, bug fixes, and infrastructure updates. We also provide comprehensive documentation covering architecture decisions, deployment procedures, API references, and troubleshooting guides. If your team prefers to maintain the software in-house, we run structured knowledge transfer sessions where our engineers walk your developers through the codebase, testing setup, and deployment pipeline. Many clients use a hybrid approach: their team handles day-to-day maintenance while engaging us for larger feature work or architectural changes.
Yes. We build focused MVPs that validate an idea by shipping only what the first users actually need and cutting the rest. The risk we design against is the MVP that spends months on features nobody uses because validation was skipped. We start with a prioritization session that sorts the feature list into must-have, nice-to-have and later phases; the MVP carries only the must-haves, usually authentication, the core value proposition and enough analytics to measure engagement. We design the architecture for growth from day one, with modular patterns and clean API boundaries, so a single-tenant launch can become multi-tenant later without a rewrite.
We use agile sprints with two-week cycles, regular demos, and async-first communication through Slack or Microsoft Teams. Every project has a shared board in Linear or Jira where you can see exactly what is being worked on, what is blocked, and what is coming next. At the start of each sprint, we plan together and agree on priorities. At the end, we demo working software and collect feedback. This keeps expectations aligned and prevents the 'build in silence for three months' anti-pattern. For day-to-day questions, we respond within business hours through your preferred messaging tool. For bigger decisions, we write short proposals with options and trade-offs rather than scheduling another meeting. We share a weekly status summary covering what was completed, what is planned, and any risks or blockers. You always have visibility into progress without needing to chase updates.

Describe the system you need

A senior engineer reads every inquiry and answers within one business day.