Work

Systems, not
screenshots.

Client work is shown at the level of architecture and responsibility. Names, internal details and figures are published only with the client's written consent.

Case 01

Discovery

Proprietary CRM and business platform

Client
Confidential client · France
Started
September 2026
Stage
Discovery
Engagement
End to end
Layers
Product · Platform · Trust

The task

The client needed its own business platform instead of adapting a generic SaaS CRM — and did not want to assemble separate vendors for development, cloud, DevOps and security.

Approach

KDS owns the full technical scope as one system: architecture, application development, infrastructure, delivery pipelines, access control and production operations.

Where it stands

Discovery first.
Then the build.

Every stage ends with something the client can see and keep. This one is still in Discovery.

  1. Now

    Discovery

    • Requirements and constraints
    • Architecture sketches
    • Access model: single sign-on and Zero Trust
    • Microservices on Kubernetes (AWS)
    • A demo environment with the interface, on the client's domain
  2. Planned

    Build

    • Go microservices
    • Data and storage design
    • Demos every 1–2 weeks
  3. Planned

    Platform & production

    • Kubernetes on AWS, described as code
    • CI/CD and environments
    • SSO, Zero Trust, mTLS, centralised secrets
    • Production rollout
  4. Planned

    Evolution

    • Ongoing development
    • Monitoring and support

Target architecture

Drawn in Discovery.
Decided on purpose.

AccessUsersWeb & internal clients
IdentitySSO · Zero TrustEvery request authenticated
Kubernetes · AWSGo microservices
svcsvcsvc
mTLS between services
DataData & storageDesigned per service
DeliveryCI/CD → GitOps → environments
TrustSecrets & certificates issued centrally, short-lived
OperationsMetrics · logs · alerts
  1. mTLS between every service

    Problem: "inside the network" is not a trust boundary.

    Trade-off: certificate issuance and rotation must be automated.

  2. Infrastructure as code from the first environment

    Problem: hand-built environments drift and can't be recreated.

    Trade-off: slower first setup, faster everything after.

  3. Short-lived credentials instead of static secrets

    Problem: leaked long-lived keys stay valid for months.

    Trade-off: services need an identity and a secrets broker (e.g. Vault) from day one.

Project
Proprietary CRM and business platformThe client needed its own business platform instead of adapting a generic SaaS CRM — and did not want to assemble separate vendors for development, cloud, DevOps and security.
Client
Confidential client · France
Status
Discovery
Scope
  • system & deployment architecture
  • Go microservices on Kubernetes (AWS)
  • CI/CD & environments
  • SSO, Zero Trust, mTLS
  • production rollout & ongoing development

Discovery draft — it will be refined as the work goes on. Implementation details are kept confidential.

Have a project in mind?
Let's build it.

Tell us about the problem in a few sentences. You'll get a reply from the engineer who would own it — within one business day.

Start a project →

or email [email protected]