Software engineering services, delivered end to end

HALDIR LTD builds and maintains software for companies that need a system to work reliably for years, not just to demo well. Below is what we actually do, how each engagement is scoped, and what you receive at handover.

Six practices · One accountable contract · Nicosia, Cyprus

01 — Practices

What we build

Each practice can be engaged on its own or combined into a single delivery team. The deliverables listed are contractual, not aspirational.

Practice 01

Custom software development

Off-the-shelf products force your company to work the way the vendor imagined. Custom software does the opposite. We model the way your business actually runs — its rules, exceptions, approvals and reporting — and build a system around it that your team can operate without a manual.

Typical work includes internal operations platforms, back-office and admin tooling, workflow automation, document and approval pipelines, and the reporting layer that finally makes the data usable.

You receive

A working system in a repository you own
Data model and architecture documentation
Automated test suite and CI pipeline
Deployment runbook and admin guide

Full details of this practice

Practice 02

Web platforms

We build web applications the way the platform intends: semantic HTML, progressive enhancement, and JavaScript used where it earns its weight. The result loads quickly on a mediocre connection, works with a keyboard and a screen reader, and is indexable when it needs to be.

That covers customer portals, multi-tenant SaaS products, dashboards, marketing sites with a real content model, and the design systems that keep them visually consistent as they grow.

You receive

Responsive interface tested on real devices
WCAG-oriented accessibility review
Performance budget and measured results
Reusable component library

Full details of this practice

Practice 03

Mobile applications

Mobile products fail on the boring things: sync conflicts, background refresh, store review, certificate expiry. We plan for those from the start, then automate the release path so shipping an update is a routine action rather than an event.

We work both cross-platform and native, choosing per project rather than by habit — and we say which one we recommend and why before you commit.

You receive

iOS and Android builds under your accounts
Offline-first data synchronisation strategy
Automated build and store submission
Crash reporting and release checklist

Full details of this practice

Practice 04

System integration & APIs

Most companies do not need another system — they need the ones they have to talk to each other. We design the contracts between them: versioned APIs, idempotent operations, retry and reconciliation logic, and enough observability to answer "where did that record go?" in minutes.

We integrate ERP, CRM, accounting, payment, identity and logistics providers, and we are comfortable working against legacy systems with imperfect documentation.

You receive

Documented REST or GraphQL interfaces
Integration map of every connected system
Error handling and reconciliation rules
Traceable event and audit logging

Full details of this practice

Practice 05

Cloud & DevOps

Infrastructure defined in code, environments that can be rebuilt from scratch, and a deployment pipeline that runs the tests before anything reaches production. Releases should be unremarkable; that is the whole goal.

We also take on migrations — moving a system from a single ageing server to a reproducible cloud setup — and we do it in stages, with a rollback path at each one.

You receive

Infrastructure as code in your repository
Staging and production parity
CI/CD pipeline with automated rollback
Monitoring, logging and alert routing

Full details of this practice

Practice 06

Quality assurance & support

Testing is part of the estimate, never a line item you can decline. Every change goes through review and an automated suite before it merges, and dependencies are audited on a schedule rather than after an incident.

After release we can stay on under a maintenance agreement: an agreed response window, a named escalation path, and scheduled updates so the system does not quietly rot.

You receive

Unit, integration and end-to-end tests
Dependency and security review reports
Defined response and escalation windows
Scheduled maintenance and update plan

Full details of this practice

02 — Engagement models

Three ways to work with us

Whichever model you choose, the commercial terms and the scope are agreed in writing before work begins.

MODEL 01

Project delivery

A defined scope, a fixed set of deliverables and an agreed timeline. Best when the problem is well understood and the outcome can be described precisely.

Written scope and acceptance criteria
Milestone-based schedule
Fixed or capped commercial terms

MODEL 02

Dedicated team

An allocated group of our engineers working continuously on your product, with priorities you set each iteration. Best for evolving products without a fixed endpoint.

Named engineers, reserved capacity
Iteration planning with your product owner
Monthly reporting and reviews

MODEL 03

Maintenance & support

Care for a system already in production — ours or someone else's. We start by auditing what exists, then agree what "healthy" means and hold it there.

Technical audit before commitment
Agreed response and resolution windows
Scheduled updates and security patching

03 — Technology

Tools chosen for the problem, not for the CV

We keep a deliberately conventional stack. Mainstream, well-documented technology means your system can be maintained by engineers who are not us — which is exactly the position you should be in.

When a project genuinely calls for something unusual, we say so, explain the trade-off, and get your agreement before committing to it.

How we choose and document decisions

Working stack

Languages: TypeScript, JavaScript, Python, Go, SQL
Backend: Node.js, FastAPI, Django, REST & GraphQL
Frontend: React, Next.js, Vue, standards-first HTML & CSS
Mobile: React Native, Swift, Kotlin
Data: PostgreSQL, MySQL, Redis, ClickHouse
Infrastructure: Docker, Kubernetes, Terraform, AWS, GCP
Quality: Playwright, Jest, pytest, static analysis

Not sure which of these you need?

Describe the situation in a few paragraphs. We will tell you what we think it needs — including when the honest answer is "less than you asked for".

[email protected] Contact details

HALDIR LTD · HE 459882 · Nicosia, Cyprus