You know your customers. We develop the software under your brand, build suitable infrastructure and provide ongoing support if you need it. One contact for product development, delivery and cluster maintenance.
Your business model becomes softwarePlan · Develop · Operate · Improve
Product and customer experienceClusters and deliveryMaintenance and dependable workflows
A new product, an existing application or a running cluster: we join where you need support.
THREE CLEAR SERVICE AREAS
Commission them separately. Let them grow together.
You can agree the complete implementation or commission development, setup or operations individually. Before each start, we document the current state, goals and responsibilities.
01 · PRODUCT DEVELOPMENT
Build your SaaS
From the first usable version to a mature product: UX, application, interfaces and automated tests within an agreed project scope.
Registration, organisations, roles and tenant isolation
Plans, subscriptions and payment providers matched to your business model
Customer area, administration, exports and interfaces
Traceable requirements, demos and documented acceptance
Your bespoke proposal describes features, milestones, rights and handover. Payment fees, content production and ongoing operations are listed separately.
We set up Kubernetes clusters or a suitable smaller environment in your cloud account, with an agreed provider or on your existing infrastructure.
Containers, infrastructure as code and documented configuration
Test and production environments, CI/CD or GitOps with a rollback path
Networking, TLS, identities, secrets and storage
Migration with a rehearsal, data reconciliation and a planned transition
Location, resources, account ownership and access are agreed before provisioning. Multiple clusters or regions are planned only when there is a specific need.
An ongoing support agreement covers the agreed systems and tasks. We can also take over existing clusters following a technical assessment.
Planned Kubernetes, operating system and component updates
Monitoring, alerting, capacity and cost visibility
Backups, agreed restore rehearsals and incident handling
Documentation, operations reports and agreed maintenance windows
Support hours, response targets, on-call cover and the included work budget are explicitly agreed. New product features and consumption charges remain separate items.
Requirements, progress, open questions and decisions are recorded in writing. You give feedback on demos and agree scope changes before implementation. Coordination can be digital and asynchronous; a phone appointment is not required.
Responsibility at each layer
We distinguish provider infrastructure, cluster, database and application. The operations plan records access, maintenance, alert recipients and responsibilities for each layer. Cluster maintenance alone does not include unlimited development of your application.
A complete handover
Agreed source code, infrastructure definitions, runbooks and data exports remain accessible. Usage rights and third-party licences are specified in the proposal. A later change of operator is prepared through access handover and an organised data export.
COSTS AND OPERATING TARGETS
A proposal with clear components.
Development is priced by project scope. Setup and migration are one-off services. Monthly support depends on the number of clusters and environments, systems, data volume and desired service hours. Infrastructure and third-party services are calculated separately.
What we need for your proposal
Your product, audience and current development stage
User numbers, tenants, expected peaks and data types
Existing systems, providers, regions and integrations
Budget range, start date and desired support hours
How long an outage may last and how much data loss is tolerable
This leads to a project and operations proposal covering scope, monthly costs, term and cancellation rules. No chargeable provisioning starts without an agreed proposal.
Our existing hosting configurator helps with providers, resources and support. Its estimate provides a basis for infrastructure planning; bespoke SaaS development effort and complex cluster services are added to the proposal separately.
Multiple replicas do not replace an independent backup. Availability, database operations and recovery are considered together. Specific commitments depend on agreed architecture, tests and service hours.
FireFlint and KoiForge may provide suitable components. We review product status, licences and interfaces for your specific use case; integrations are agreed separately.