Kotlin development
Kotlin development for backends that last
We develop backends, APIs and microservices in Kotlin. Kotlin runs on the JVM, interoperates directly with existing Java code and prevents whole classes of bugs through null safety. We build new systems, migrate Java to Kotlin step by step and add AI features to existing services.
You speak to Kevin or Pascal directly. The intro call takes 30 minutes.
Updated
When to call us
- You are looking for a senior Kotlin developer or small team for a backend or API.
- You want to move a Java codebase to Kotlin gradually, without a big bang.
- Your backend needs AI features, such as search over your own data or an agent.
- Your team lacks experience with architecture, testing or CI/CD on the JVM.
Not the right fit. There are two of us. We do not supply a team of ten; we do supply a senior who joins temporarily or a bounded project.
Java
public Optional<Invoice> latestSent(Customer customer) {
if (customer == null || customer.getInvoices() == null) {
return Optional.empty();
}
return customer.getInvoices().stream()
.filter(i -> i.getStatus() == Status.SENT)
.max(Comparator.comparing(Invoice::getDate));
}Kotlin
fun latestSent(customer: Customer?): Invoice? =
customer?.invoices
?.filter { it.status == Status.SENT }
?.maxByOrNull { it.date }What you get
Backends and APIs
REST and event-driven services with a clear domain layer, automated tests and documentation.
Java to Kotlin
Step-by-step migration in which Java and Kotlin run side by side and every step can go live.
Microservices and integrations
Integrations with payment, CRM and ERP systems, with attention to error handling and idempotency.
CI/CD and cloud
Automated build, test and deployment in containers on AWS, Azure or your own infrastructure.
How we approach it
Technology
- Kotlin
- JVM
- Spring Boot
- Coroutines
- Gradle
- PostgreSQL
- Docker
- AWS
- Azure
- CI/CD
- 01
Step into what exists
We read the existing code and the team's conventions before proposing anything.
- 02
Small, reviewable steps
Every change is one pull request with tests, so your team can read along and roll back.
- 03
Transfer knowledge
We record choices and work with your developers, so the knowledge stays in your organisation.
Proof from our own work
Over ten years of Java and Kotlin in sectors where software cannot be allowed to fail: logistics and ports, mobility, energy and financial services.
The same discipline in other work: additive changes and automated checks on every system we maintain.
Shipping software with AI agents, safely and verifiably
Frequently asked questions
Why Kotlin instead of Java?
Kotlin is more concise, has null safety in the type system and offers coroutines for asynchronous work. It runs on the same JVM and uses the same libraries, so your existing Java investment remains usable.
Can Kotlin and Java live side by side in one project?
Yes. Kotlin and Java call each other without a bridging layer. That lets you migrate per file or module and keep shipping in the meantime.
Can you join our existing team?
Yes. We work in your repository, following your review and release process, and take responsibility for a bounded part or advise on the architecture.