BlueID
BlueID's lock storage clearance reached production, built by Datics inside its team
BlueID, based in Munich, runs a platform for secure mobile keys that open real locks. We built lock storage clearance, a feature its architect called very important for its customers, inside BlueID's own team and process, and it went to production without issues.
B2B SoftwareSecure mobile key platformModernized a live product
- Shipped
- Lock storage clearance, live in production
- Also built
- Access token, invitation and template APIs
- Rhythm
- Weekly goals and retros with BlueID's architect
- Runs in
- BlueID's own AWS environment
The challenge
BlueID was restructuring its live key platform and revamping its web apps, and wanted more engineering that worked under its own technical lead rather than beside it.
What we did
We worked inside BlueID's tools and weekly goals, and built lock storage clearance, access token, invitation and template APIs into its existing services, one API at a time.
The outcome
BlueID's architect reported lock storage clearance complete, with its first API in production and running without any issue.
The starting point
BlueID makes secure mobile keys for real things: a platform with an identity service and an access control service, used by its customers, and web apps run by its own web team.
What had to change
BlueID was developing and restructuring its application and revamping its web apps. It needed engineering that would learn a security domain quickly and ship into the live product under its own technical direction.
What could not break
- BlueID's architect sets the technical direction
- Customers keep using the live platform while services change
- Work lives in BlueID's own issue tracker, wiki and chat
- Every release lands in BlueID's own AWS environment
- Knowledge stays with BlueID when the engagement ends
The calls we made
We treated the platform as BlueID's product and BlueID's call: its architect kept technical authority, and we owned delivery of each feature inside that.
- 01
Let BlueID's architect choose and train the team
BlueID vetted our engineers through its own coding assignments and interviews, and its architect later worked with us on site to deepen domain knowledge.
Ruled outEngineers chosen and onboarded by us alone.
- 02
One API at a time into live services
Each API was built, tested and released on its own, so customers on the live platform never waited for a large batch.
Ruled outHolding work back for one big release.
- 03
Tests before production
Lock storage clearance shipped with unit and integration tests, because it sits in the access token side of a security product.
Ruled outTesting only by hand before release.
- 04
Start small and earn more scope
The frontend work began with two trial periods before the commitment grew, so BlueID could judge the work before relying on it.
Ruled outA large commitment before any work was seen.
How the system fits together
What we built
Lock storage clearance
A feature BlueID's architect called very important for its customers, built with unit and integration tests. Its first API went to production and ran without any issue.
Access token APIs
APIs for cancelled access tokens and their confirmation, then paging for cancelling large numbers of card tokens at once.
Invitation and template APIs
Admin only APIs for BlueID's operator portal to manage message templates and send invitations, documented in Swagger for BlueID's staff.
What changed
BlueID's architect reported lock storage clearance complete, a feature he called very important for BlueID's customers, with its first API in production and running without any issue. The work was later handed over to BlueID's own backend team.
Under the hood
- Datics role
- Forward deployed engineering
- Access
- BlueID's issue tracker, wiki, chat and AWS environment, granted by its architect, with onboarding on its identity and access control services.
- Process
- Weekly goals and retros with BlueID's architect and product owner, and each API released into the live platform on its own.
Cloud and infrastructure
Apps and APIs
Also in the stack
How it shipped
Vetted by BlueID
BlueID's architect tested candidates with its own assignments and interviews before anyone joined its tools.
Operator portal APIs
Invitation and message template APIs first, released into the operator portal, while we learned the platform.
Tokens and lock storage clearance
Cancelled token APIs and lock storage clearance, each tested and released on its own, with the first clearance API in production.
Tenancy and handover
Tenant and customer signup APIs, then a handover of the work to BlueID's own backend lead.
In BlueID's tools
We worked in BlueID's issue tracker, wiki and chat, with weekly goals and retros set by its architect.
Its architect in our office
BlueID's architect worked on site with us to train the team in the platform's domain, which BlueID's CEO valued.
Documented to hand over
Our engineer documented the token state lifecycle on his own initiative, and the work was handed to BlueID's backend lead at the end.
What this unlocked
BlueID took the backend in house, with the work handed over to its new backend lead, a handover we plan for in every forward deployed engagement.
Related work
Have a product with the same kind of constraints?
Tell us what already exists and what you want it to do. We will tell you what it takes.