Codiaks.
Menu
Services Work Process Clients Book a call
Codiaks Service · 01

Custom software, written to run for years.

Greenfield platforms, legacy modernization, internal tools, and complex integrations. We write production code with the engineering rigor that keeps it running long after launch — and the same team stays to maintain it.

Book an intro call See custom software work
7+
years in production
Tier-1
bank deployments
P@SHA
Gold · 2024
trade-iq/src/services/screener.ts
// Production transaction screener — live since 2019
import { Compliance, Tracer } from '@codiaks/core'
export class TransactionScreener
implements Compliance.Engine {
async screen(tx: Transaction) {
return await tracer.trace('screen', async () => {
const flags = await rules.evaluate(tx)
return new ScreenResult({ tx, flags })
})
}
}
deployed · multi-region
v3.42.1 · ✓ tests passing
What we do

Six things we build, built six different ways.

Every engagement is shaped to its work. The shared posture is engineering rigor: code review on every PR, architecture decisions documented, integration with your existing stack, and a team that stays.

Greenfield platforms

New products, end to end. Architecture, design, code, deployment, and the runbooks to keep them running once you take over.

Legacy modernization

Rewrites, refactors, replatforming. Keep the value, drop the technical debt, ship without breaking the production system you already depend on.

API platforms & integrations

REST, GraphQL, gRPC, event-driven. Internal APIs, partner APIs, and the gnarly integrations between systems that need to talk.

Internal tools & admin

Operations dashboards, admin panels, internal workflows. Tools your team actually uses because they were built around the work they actually do.

Database & data

Schema design, migrations, query performance, replication. Data systems that scale with the business and recover when something goes wrong.

Performance engineering

Make slow things fast. Profiling, caching, query optimization, async pipelines. We measure first, then change one thing at a time.

How we engage

Four stages. Same team across all four.

Stage 01

Discovery

Two to four weeks. We map the system, the constraints, the regulatory landscape, and the outcomes that matter. Output is a written engagement plan.

Stage 02

Architecture

We design before we code. ADRs document trade-offs. Reviews with your team. The decisions that are easy to change later get made fast; the ones that aren’t get made carefully.

Stage 03

Build

Code review on every PR. Tests on every change. Integration with your stack from day one. Your team sees what we’re shipping every week.

The one that matters
Stage 04

Maintain

Same engineers. Years on. Extensions, refactors, security patches, performance work, new features. The system gets better with use because the people who built it keep working on it.

Featured Work

Trade iQ. Built end-to-end since 2019.

Trade iQ Custom platform · 2019 → ongoing

A trade compliance platform we designed, built, and continuously operated for seven years.

End-to-end custom build — architecture, code, infrastructure, design, integrations. Now deployed at Standard Chartered, HBL, Citibank, and AML Authority. The original engineer who wrote the first commit is still on the account.

7+
years in production
4
continents deployed
85%
faster screening
Stack

Tools we’re fluent in. Tools we’re willing to learn.

We pick the stack that fits the work, not the trend. If your team uses something we don’t list, we’ll either pick it up or tell you honestly that someone else is a better fit.

Languages
TypeScript Python Go Java .NET Rust
Frontend
React Next.js Vue Svelte Tailwind
Data
PostgreSQL MySQL Redis Kafka ClickHouse
Cloud
AWS Azure GCP Kubernetes Docker
Questions we get

Things prospects ask on the first call.

How do you handle existing legacy codebases?
We start by reading. A week or two of just understanding what’s there, what works, what doesn’t, and why. Most legacy code is the way it is for a reason — usually a constraint that’s no longer obvious. We document the system, then propose a path: rewrite, refactor, replatform, or leave alone. Whatever happens, we don’t break production.

What’s a typical engagement length?
Initial builds run 3 to 9 months depending on scope. Most engagements then continue indefinitely — the same team that built it maintains, extends, and re-architects as the business shifts. Trade iQ has been running 7 years and counting. Smaller engagements (a single platform module, a focused integration) can be done in 6 to 12 weeks.

What if our requirements change mid-build?
They will. Every engagement we’ve ever done has had at least one significant pivot. We architect for change in the parts of the system that are likely to change, and harder decisions in the parts that aren’t. When the pivot happens, we re-scope honestly — sometimes that means more time, sometimes less, never silently.

Who owns the IP?
You do. Code, designs, documentation, runbooks, test suites — everything we produce on your engagement is yours. We sign work-for-hire agreements as standard. Open-source components keep their original licenses; we’ll flag any obligations during architecture.

How do you ensure quality at scale?
Code review on every PR. Architecture reviews for substantive changes. ADRs documenting decisions. Tests required for new features. Static analysis and security scans in CI. Integration tests against real environments. None of this is optional or upgraded for premium tiers — it’s how we work on every engagement.
Talk to us

Tell us what you’re building.

Book a 30-minute intro call. We’ll listen, ask hard questions, and tell you plainly whether we’re the right team to build it.

Get in touch hello@codiaks.com
Or explore other services
Product Design → DevOps → QA & Testing → Security →