Discuss your project

Services

What we do,and what itchanges.

Nine services, each shaped by a class of problem that keeps arriving. Below: the situations that lead to each engagement, what you receive, how it runs and what typically follows.

Discuss your project See technical capabilities

Filter services

Showing 9 of 9 services

01

Enterprise Software Development

Long-lived business systems built around an explicit domain model, with the operational and security properties an enterprise needs from day one.

What it solves

Core business systems accumulate undocumented behaviour, brittle integrations and unclear ownership. Change becomes slow and risky, and the cost of every new requirement rises.

Outcome: A system your team can extend without fear, with the reliability, auditability and security characteristics the business actually requires.

Who it is for

  • Organisations replacing a core system that has become too expensive to change
  • Companies whose operations depend on internal software built years ago
  • Product teams that need senior engineering capacity without rebuilding a department

What you receive

  • Domain and architecture documentation with recorded decisions
  • Production-ready service and application code with automated test coverage
  • Infrastructure definitions and reproducible deployment pipelines
  • Data migration plan and executable migration tooling

How the engagement runs

  1. Discovery1–3 weeks
  2. Architecture2–4 weeks
  3. DeliveryOngoing
  4. Transition2–4 weeks

Common use cases

  • Operations and workflow platforms
  • Internal tooling that replaces spreadsheet-driven processes
  • Customer and partner portals with role-based access
  • Back-office systems with audit and approval requirements

Technologies

  • Go
  • Python
  • TypeScript
  • Angular
  • PostgreSQL
  • MongoDB
  • Redis
  • NATS
  • RabbitMQ
  • Elasticsearch
  • Kubernetes
  • Docker
  • OpenTelemetry

02

Mobile Application Development

Native and cross-platform applications for workforces and customers, built to work under poor connectivity and enterprise device policy.

What it solves

Mobile projects are often scoped as a smaller version of the web product, then fail on the things that are specific to mobile: offline behaviour, background sync, device management, store review and long-term OS churn.

Outcome: An application people can actually use where the work happens, and a release process your team can run without us.

Who it is for

  • Organisations with a deskless or field workforce
  • Companies whose customers expect a first-class mobile experience
  • Teams whose existing app has become expensive to release or maintain

What you receive

  • Application source, delivered into your repositories
  • Offline and synchronisation design with documented conflict rules
  • Automated build, signing and distribution pipeline
  • Crash reporting, analytics and release health dashboards

How the engagement runs

  1. Discovery1–2 weeks
  2. Design & architecture2–4 weeks
  3. BuildOngoing
  4. Launch & support4+ weeks

Common use cases

  • Field service and workforce management applications
  • Inspection, audit and compliance capture
  • Logistics and proof-of-delivery applications
  • Secure customer applications with strong authentication

Technologies

  • Swift
  • Kotlin
  • TypeScript
  • Go
  • SQLite
  • PostgreSQL
  • Redis
  • Firebase
  • OpenTelemetry
  • Kubernetes

03

Cybersecurity Consulting

Security embedded in architecture and delivery: threat modelling, secure design review, and practical remediation your engineers can execute.

What it solves

Security arrives as a report at the end of a project. The findings are real, the deadline is fixed, and the team ships anyway with a list of accepted risks that never gets closed.

Outcome: Fewer findings late, a shorter path from finding to fix, and an engineering team that can reason about its own threat surface.

Who it is for

  • Engineering organisations building systems that handle regulated or sensitive data
  • Security teams that need engineering depth, not another checklist
  • Companies preparing for a customer security review, certification or due diligence

What you receive

  • Threat model with documented trust boundaries and abuse cases
  • Authentication and authorisation architecture review
  • Secure design review of new or changed architecture
  • Prioritised remediation plan with owners and effort estimates

How the engagement runs

  1. Scoping1 week
  2. Assessment2–4 weeks
  3. Plan1 week
  4. SupportOngoing

Common use cases

  • Security architecture for a new platform
  • Preparing for external penetration testing or certification
  • Responding to a customer security assessment
  • Reviewing an acquisition target’s technical estate

Technologies

  • HashiCorp Vault
  • OpenID Connect
  • OAuth 2.1
  • SPIFFE
  • Kubernetes
  • Terraform
  • OPA
  • Trivy
  • Semgrep
  • OpenTelemetry

04

Security Audits & Vulnerability Assessments

Evidence-based assessment of applications, APIs, cloud configuration and architecture, with findings written so they can be fixed.

What it solves

Automated scans produce volume, not clarity. Teams receive hundreds of findings without exploitability context, business impact or a realistic fix, and the important issues get lost.

Outcome: A short, ordered list of what to fix first, evidence you can show a customer or auditor, and a re-test that confirms the fix.

Who it is for

  • Teams preparing for launch, certification or a customer security review
  • Organisations that inherited a system and need to know its real posture
  • Investors and acquirers assessing technical risk

What you receive

  • Executive summary written for non-technical decision-makers
  • Technical findings with reproduction steps, evidence and affected components
  • Risk rating combining exploitability, business impact and exposure
  • Specific remediation guidance per finding, with effort estimates

How the engagement runs

  1. Scope & authorisation3–5 days
  2. Assessment1–3 weeks
  3. Reporting1 week
  4. Re-testAfter remediation

Common use cases

  • Pre-launch application and API assessment
  • Cloud configuration and identity review
  • Authentication and authorisation assessment
  • Third-party and dependency risk review

Technologies

  • Burp Suite
  • OWASP ZAP
  • Semgrep
  • Trivy
  • Nuclei
  • Terraform
  • Kubernetes
  • AWS IAM
  • Azure Entra ID

05

Palantir Foundry Development & Consulting

Ontology design, pipeline engineering, operational applications and enablement for organisations delivering on Palantir Foundry.

What it solves

Foundry programmes often stall between data integration and operational use. Pipelines land, dashboards appear, and the decisions the platform was bought to improve still happen in spreadsheets.

Outcome: Decisions made inside the platform, against data the business trusts, by people who did not need to become data engineers.

Who it is for

  • Organisations that have licensed Foundry and need delivery capacity
  • Teams with pipelines in place but no operational adoption
  • Programmes that need an independent partner alongside their platform vendor

What you receive

  • Ontology design: object types, link types, actions and permission model
  • Data transformation pipelines with tests and quality checks
  • Operational applications and writeback workflows
  • Integrations with source systems, both modern and legacy

How the engagement runs

  1. Assessment2 weeks
  2. Ontology & design3–5 weeks
  3. BuildOngoing
  4. Enablement3–6 weeks

Common use cases

  • Supply chain and logistics operations
  • Asset and maintenance management
  • Manufacturing and production planning
  • Financial operations and reconciliation

Technologies

  • Palantir Foundry
  • Python
  • PySpark
  • SQL
  • TypeScript
  • Go
  • PostgreSQL
  • Kafka
  • REST and gRPC integrations

06

Data Platforms & Enterprise Integration

Connecting systems that were never designed to talk to each other, with contracts, lineage and quality checks that keep the result trustworthy.

What it solves

Every system holds part of the picture. Integrations were built point-to-point over years, nobody owns the contracts, and reconciliation happens manually in a spreadsheet at month end.

Outcome: Reliable data movement between systems, a single reconciled view of the operations that matter, and integrations that survive their source systems changing.

Who it is for

  • Organisations running a mix of modern and legacy systems
  • Companies post-merger with duplicated and conflicting system estates
  • Teams whose reporting is manual because nothing agrees

What you receive

  • Data contracts and integration architecture documentation
  • Event-driven and batch pipelines with automated tests
  • Change-data-capture and legacy adapter services
  • Data quality checks with alerting and ownership

How the engagement runs

  1. Landscape review2 weeks
  2. Architecture2–4 weeks
  3. DeliveryOngoing
  4. Handover2–3 weeks

Common use cases

  • Consolidating operational data across business units
  • Post-merger system integration
  • Migrating from point-to-point integrations to an event backbone
  • Building a reporting layer that does not touch production databases

Technologies

  • Go
  • Python
  • PostgreSQL
  • MongoDB
  • Kafka
  • NATS
  • RabbitMQ
  • Redis
  • Elasticsearch
  • Debezium
  • Airflow
  • dbt
  • Kubernetes
  • OpenTelemetry

07

Cloud & Infrastructure Consulting

Infrastructure designed for the reliability and cost profile the business needs — reproducible, observable and operable by your own team.

What it solves

Cloud estates grow by accident. Environments drift, nobody can rebuild production from source, costs rise faster than usage, and reliability depends on the two people who remember how it was set up.

Outcome: Environments that can be rebuilt from a repository, costs that track usage, and an on-call rotation that is survivable.

Who it is for

  • Teams whose infrastructure has outgrown its original design
  • Organisations facing reliability or compliance requirements they cannot currently evidence
  • Companies whose cloud spend has decoupled from business volume

What you receive

  • Target architecture with documented reliability objectives
  • Infrastructure-as-code covering every environment
  • CI/CD pipelines with automated, reversible deployments
  • Observability stack: metrics, logs, traces and meaningful alerts

How the engagement runs

  1. Assessment1–2 weeks
  2. Target architecture2–3 weeks
  3. ImplementationOngoing
  4. Operational handover2–4 weeks

Common use cases

  • Cloud migration and re-platforming
  • Kubernetes platform design and hardening
  • Multi-environment and multi-region architecture
  • Reliability engineering and incident practice

Technologies

  • Kubernetes
  • Docker
  • Terraform
  • Helm
  • ArgoCD
  • Prometheus
  • Grafana
  • OpenTelemetry
  • HashiCorp Vault
  • PostgreSQL
  • Redis
  • NATS

08

Software Architecture & Technical Strategy

Independent architectural assessment and technical decision support for leaders who need a defensible answer, not a vendor’s preference.

What it solves

Significant technical decisions are made with incomplete information, under time pressure, often on advice from a party with an interest in the outcome. The consequences appear years later.

Outcome: A decision your leadership can stand behind, and a plan your engineers can execute.

Who it is for

  • CTOs and engineering leaders facing a decision above their comfortable risk threshold
  • Boards and investors needing an independent technical view
  • Organisations planning a modernisation programme

What you receive

  • Architecture assessment with findings and evidence
  • Options analysis with cost, risk and timeline per path
  • Technical due diligence report
  • Build-versus-buy analysis

How the engagement runs

  1. Framing3–5 days
  2. Assessment2–4 weeks
  3. Analysis1–2 weeks
  4. Briefing1 week

Common use cases

  • Rebuild versus refactor decisions
  • Platform and vendor selection
  • Technical due diligence before investment or acquisition
  • Post-acquisition integration planning

Technologies

  • Stack-independent — assessments cover whatever is in place
  • Common estates: Java, .NET, Go, Python, Node.js, PHP
  • Cloud: AWS, Azure, Google Cloud, on-premise and hybrid
  • Data: PostgreSQL, Oracle, SQL Server, MongoDB, Kafka

09

Technical Due Diligence

An independent, evidence-based view of a technology estate for investors and acquirers — what it is, what it costs to own, and what could go wrong.

What it solves

Technology is a growing share of what gets acquired, and the diligence on it is often a management presentation and a repository tour. The expensive surprises — an unmaintainable core, a licence problem, a security posture that fails the first customer review — appear after completion.

Outcome: A defensible view of the technical asset, the cost to own and integrate it, and the conditions worth putting in the agreement.

Who it is for

  • Investors and acquirers assessing a software or technology-dependent target
  • Boards seeking an independent view before a significant technology commitment
  • Sellers preparing an estate for scrutiny ahead of a transaction

What you receive

  • Technical due diligence report with findings, evidence and ratings
  • Architecture and infrastructure assessment
  • Security posture assessment against the claims made
  • Open-source licence inventory and compliance findings

How the engagement runs

  1. Scoping2–3 days
  2. Assessment1–3 weeks
  3. Report and briefing1 week
  4. Post-completionOn request

Common use cases

  • Acquisition of a software or technology-dependent company
  • Investment round where technology is the principal asset
  • Post-completion technical integration planning
  • Vendor due diligence ahead of a sale

Technologies

  • Stack-independent — whatever the target runs
  • Common estates: Java, .NET, Go, Python, Node.js, PHP
  • Cloud: AWS, Azure, Google Cloud, on-premise and hybrid
  • Tooling: Semgrep, Trivy, licence scanners, delivery analytics

Not sure whichengagement fits?

Describe the problem rather than the service. We will tell you which of these applies, whether it needs one engagement or three, and what a realistic first step looks like.

Discuss your project Explore services first

An engineer reads every enquiryNo pursuit if we are not the right fit

Senior engineering for operations platforms, security architecture and Palantir Foundry delivery — for organisations where a wrong answer stops the business.

Based inVilnius, LithuaniaWorking acrossEurope · United Kingdom

Contact

Discuss your project

Project enquiries, security disclosures, applications and data requests all arrive through the form, in one queue. A person replies typically within one working day.

BYAK MBsmall partnership (mažoji bendrija)Company code 306897734Krivių g. 5, LT-01204 Vilnius, LithuaniaRegister of Legal Entities of the Republic of Lithuania

© 2026 BYAK MB. All rights reserved.

Palantir and Palantir Foundry are trademarks of Palantir Technologies Inc. BYAK is an independent engineering company and is not affiliated with Palantir Technologies Inc.