Open to conversations

Piyush Sardana

Lead Architect · solution and security architecture for identity, authorization and cloud-native IoT platforms

I design the parts of a platform everything else depends on: who can log in, what they're allowed to do, and how devices and services talk to each other. Then I make the right way the easy way, so teams adopt it without a mandate.

IAM · CIAM · Zero Trust · OAuth/OIDC · RBAC/ABAC · Policy-as-code · API security · Kubernetes · Kafka · Azure · IoT · IT/OT · TOGAF

14+years building software
~10years in identity and access
100+architecture decisions authored or co-authored
~250microservices under the architecture governance I run

Where I go deep

Three areas, built up over a decade

Architecture leadership

Governance that teams adopt because it helps them

I lead architecture across many teams and grow the people who make the decisions.

  • Lead a cross-team architecture board, with rotating reviewers
  • Coach architects and engineers to make sound calls themselves
  • Run communities of practice and shared patterns
  • Inception canvases, decision records sized to the risk, and C4 and arc42 that people read
  • Modernisation from legacy to target architecture without stopping delivery
ADRsarc42C4TOGAF

Identity and authorization

One identity layer, and authorization teams own

Customers, partners, staff and machines, from single sign-on to fine-grained policy.

  • Federated authorization that became the company standard: policy-as-code, central enforcement and audit
  • Identity configuration as code across several Keycloak instances
  • Token-based API security for partner integrations
  • AI agents treated as non-human identities, each with least-privilege access
KeycloakOAuth/OIDCOPA/OPALMCP

Cloud-native and IoT platforms

From the device edge to the cloud

Platforms where operational technology meets IT, built so the secure, observable path is the default.

  • Device fleets: local control, secure firmware updates, device identity with mTLS
  • Event-driven data: streams instead of shared databases, with schema governance
  • Kubernetes platforms, operators and shared building blocks
  • Security and regulation by design: Cyber Resilience Act, GDPR
KubernetesKafkaMQTTAzure

How I decide

Principles from 100+ architecture decisions

Start with the problem on one page

Before any design, an architecture inception canvas gets goals, constraints, quality targets and stakeholders agreed on a single page. The decision record comes after, not instead.

Rigour matched to how reversible a choice is

One-way doors get a full review with security in the room. Reversible ones get a one-paragraph record and a date to revisit.

The simplest model that fits

Pick the approach the problem actually needs, not the most powerful one.

A standard isn't done until teams use it

Adoption is the test. If a team works around a standard, the standard has a gap.

Side projects

Where I try patterns before I recommend them

IoT observability · in progress

Follow every IoT reading from device to dashboard

A tracer that follows every IoT reading from the device to the dashboard and shows where and why data goes missing.

Product owner, architect and developer

Key features

  • Follows each reading hop by hop, from the device through brokers, streams and services to the app, and shows exactly where it stopped
  • Explains why a reading was lost: rejected, schema break, payload change or lost on the device link
  • Watches pipelines read-only, so production systems need no changes
  • One small instrumentation contract across six languages and embedded devices
  • Device kinds as configuration: gateways, devices behind them and many message channels, with no code per device type
  • Shows when aggregated values were built from incomplete data

Built with

GoOpenTelemetryClickHouseMQTT 5Apache KafkaProtobufJSON SchemaDockerJava · Python · .NET · Rust · Node.js · C

Planned

AWS IoT CoreAmazon MSKKinesis Data StreamsAzure IoT HubAzure Event HubsConfluent Schema Registry

Smaller ones: a mobile reading library on AWS, a tool for exercising GDPR rights, an app that puts museum art on your TV, and agent tooling where approvals and spending stay with a person.

Experience

14+ years across Java, .NET, Python and TypeScript

Lead Architect (R&D) · SENEC

2024 — now

Architecture governance and the identity and authorization platform for a cloud-native IoT energy platform; lead the IAM team and the Architecture Circle of Excellence.

Senior Software Engineer · Forto

2022 — 2023

Designed the IAM platform for a digital freight-forwarding company on Keycloak, OneLogin and OPA; built authorization services and brought in contract and load testing.

Tech Lead · Futurice

2022

Technical direction for client projects in consulting; mentoring and technical hiring.

Lead Software Engineer · Verivox

2019 — 2021

Led a consumer comparison platform from a monolith to .NET Core microservices on Kubernetes using domain-driven design; set CI/CD and testing standards.

Senior Software Developer · Columba OIM

2016 — 2019

.NET Core microservices and APIs for an identity-management product: where the identity specialism started.

Software Developer · EPAM Systems

2012 — 2016

Enterprise web and mobile applications; CI/CD and release automation.

Let's talk

Open to conversations about architecture roles, or about identity, policy-as-code and platform architecture.

[email protected] · Berlin · hybrid or remote