Free e-book: IEEE 802.15.4ab vs IEEE 802.15.4z

A vehicle access system has to know exactly where the key is - not just that it's near.

Q: What is a vehicle access system (VAS)?

A vehicle access system is the complete system that lets a phone or device unlock, start, and interact with a car - combining a secure digital key, relay-resistant ranging, precise localization, and the integration into the vehicle. It's more than a key: it has to know exactly where the key is and confirm it's genuinely there. needCode builds the whole system, not just one part.

Q: How is a vehicle access system different from a digital key?

A digital key is the credential that identifies the user and authorises access, while a vehicle access system is the whole system around it - the secure ranging that stops relay attacks, the localization that places the key precisely, and the integration with the car's doors and start. The key alone can't tell where it is or whether it's really there. The system is where the security and the experience actually live.

Q: Why is localization the hard part of vehicle access?

Localization is hard because a car has to know not just that the key is near but exactly where - outside at the driver's door, inside the cabin, in the boot zone, or just walking past - which requires multiple UWB anchors around the car, fused, rather than a single proximity check. Getting it wrong means the car behaves incorrectly or insecurely. It's the part that decides whether passive entry feels effortless and stays safe.

Q: How does a vehicle access system prevent relay attacks?

It prevents relay attacks with time-of-flight secure ranging - UWB, and BLE Channel Sounding where the radio fits - which measures the key's real physical distance, something a relay can't forge because relaying only adds delay. Access is granted on genuine proximity, not a relayed signal. needCode builds this as the security core of the system.

Q: Does it support passive entry and walk-away lock?

Yes - needCode's vehicle access systems support passive (approach) entry that unlocks the right door as the driver nears, and walk-away lock that secures the car as the key moves away, both driven by precise localization. The car acts because it knows where the key is. The same localization enables zone-aware actions like opening the boot.

Q: UWB or BLE for vehicle access?

UWB is the basis of the CCC Digital Key approach and gives both the highest-assurance secure ranging and the precise multi-anchor localization a vehicle access system needs, while BLE Channel Sounding brings relay-resistant ranging to the BLE radio where that fits the design. Many systems use both. needCode builds both and advises based on the security target and the vehicle's design rather than a single radio.

Q: Does it meet the CCC Digital Key standard?

Yes - needCode builds vehicle access to the CCC Digital Key and Aliro standards, with UWB secure ranging as the CCC-aligned approach, as an active FiRa and UWB Alliance contributor. The credential, ranging, and localization are built to the standard the automotive industry is converging on. The implementation is done by people shaping those specs.

Q: Can you build the whole system or just parts?

needCode can build a complete vehicle access system end to end, or any component of it - the digital key, the secure ranging, the localization, or the integration. The system rolls up needCode's digital-key, relay-defense, and UWB localization work into one coherent build. A programme can bring needCode in for the hard core (localization and ranging) or for the whole thing.

Q: Do you have automotive experience for this?

needCode's UWB secure ranging, RTLS-grade localization, and BLE Channel Sounding depth are directly applicable to vehicle access, built to CCC and FiRa, and these are exactly the disciplines a VAS demands. The proof is in that ranging and localization work rather than a named automotive production deployment, so needCode is honest that automotive evidence is transferable. It is a near-perfect fit for needCode's core strengths.

needCode builds complete vehicle access systems - the secure digital key, the relay-resistant ranging, and the precise localization that together let a car unlock as the driver approaches, start only when the key is inside, act by zone, and lock as they walk away. It sits exactly where needCode's strengths converge: UWB ranging, secure ranging, RTLS-grade localization, BLE, and digital-key standards, in one team.

Book a discovery call

How it works

We work with Industry Leaders

A digital key unlocks a car. A vehicle access system knows where the key is - and that's the hard part.

Unlocking a car from a phone is the easy half. The hard half is everything a real access system has to get right: where exactly is the key - outside at the driver's door, inside the cabin, in the boot zone, or just walking past - and is it really there, or is a relay faking it? A car that can't localize the key precisely either behaves wrong (unlocking the wrong door, refusing to start) or insecurely (granting access on a relayed signal). Localization, not the credential, is where a vehicle access system is won or lost.

needCode builds the whole system, and it's a near-perfect fit for what we do best: UWB secure ranging for relay-resistant proximity, multi-anchor UWB localization for precise in/out and zone awareness, BLE Channel Sounding where it fits, and the CCC digital-key credential tying it together. One team builds the key, the ranging, the localization, and the integration - not four vendors who have to be made to agree.

Knows exactly where

Multi-anchor UWB localization - which door, inside or outside, which zone - not just "near."

Can't be relayed

Time-of-flight secure ranging, so access is granted on real proximity, never a relayed signal.

One system, one team

Digital key, ranging, localization, and integration built together, not stitched from vendors.

What a vehicle access system takes

Four layers turn a phone into a car key that's secure and precise. needCode builds all four.

Secure Digital Key

The phone- or device-based credential - CCC Digital Key and Aliro - that identifies the user and authorises access, cryptographically and revocably. It's the identity layer the rest of the system trusts.

Digital Keys & Access

Relay-Resistant Secure Ranging

Time-of-flight ranging - UWB, and BLE Channel Sounding where it fits - so the car grants access on the key's real physical distance, which a relay can't forge. Without it, a digital key is a relay attack waiting to happen.

Relay Attack Prevention

Precise In/Out Localization

Multiple UWB anchors around the car, fused, to place the key precisely - which door, inside the cabin or outside, which zone - not just "in range." This is the hard, differentiating part, and what lets the car behave correctly and securely.

UWB RTLS Design & Deployment

Indoor Positioning (RTLS)

Mesh Firmware & Stack

The certified BLE Mesh stack, the mesh models, and the connection firmware beneath them - built to the Bluetooth SIG specification by the team that co-authored it. It's the foundation everything else rests on, and needCode brings both the certified stack and the depth to extend it for product-specific models and behaviour.

Multi-Protocol / Coexistence

Building a vehicle access system?

Book a discovery call with our CEO

Book a discovery call

The experiences it enables

Precise localization isn't a spec - it's what makes the access experience work. Four it powers.

Passive / Approach Entry

The car recognises the driver approaching and unlocks the right door automatically - no button, no app open - because it knows exactly where the key is. The localization is what makes passive entry feel effortless instead of unreliable.

Secure Engine Start

The car allows start only when the key is genuinely inside the cabin, verified by localization rather than mere proximity. It's the difference between convenience and a car that could drive off on a relayed signal.

Relay Attack Prevention

Zone-Aware Actions

Different zones trigger different actions - the boot opens when you're behind the car with full hands, the right door unlocks at your approach. Zone awareness turns precise localization into a better everyday experience.

Walk-Away Lock & Key Sharing

The car locks automatically as the key moves away, and digital keys can be shared and revoked from a phone. Both depend on the system reliably knowing where the key is and whose it is.

Digital Keys & Access

Why teams build vehicle access with needCode

Exactly where our strengths converge

A vehicle access system needs UWB ranging, secure ranging, precise localization, BLE, and a digital-key credential - and those are precisely needCode's core disciplines. Few teams have all of them; needCode builds the whole stack.

Secure ranging is our home ground

needCode is the largest dedicated UWB team in Central Europe and a certified Qorvo partner - the relay-resistant ranging at the heart of secure access is exactly what we build, with the public QM35 SDK to show for it.

Localization, not just proximity

needCode's UWB RTLS and positioning depth is what turns "the key is near" into "the key is at the driver's door, outside" - the precise localization a real access system runs on. It's the hard part, and a core competence.

One team for the whole system

needCode builds the key, the ranging, the localization, and the integration together, with multi-radio coexistence designed in. The system is coherent because one team owns all of it, not assembled from vendors who never met.

Four ways to bring needCode in

From a system architecture to a fully integrated vehicle. We match the engagement to where the programme is.

01 Access System Architecture

Duration:
2–4 weeks
Best for:
Designing the access system - radios, localization, credential, and integration
Deliverable:
System architecture, ranging/localization approach, leadership readout

02 Localization & Ranging Build

Duration:
Phased
Best for:
Building the UWB localization and secure ranging - the hard core of the system
Deliverable:
Working multi-anchor localization and relay-resistant ranging

03 Full VAS Integration

Duration:
Phased
Best for:
Integrating the key, radios, and localization into the vehicle's systems
Deliverable:
An integrated, coexisting vehicle access system

04 Long-Term Team

Duration:
Multi-year, retainer-based
Best for:
Owning the access system across a vehicle programme and its life
Deliverable:
A dedicated access / ranging team

What we ship on

The localization, ranging, credential, and integration a vehicle access system runs on.

Localization & ranging

UWB time-of-flight (TWR)

UWB AoA

multi-anchor localization

BLE Channel Sounding

proprietary PBR solvers

Credential & standards

CCC Digital Key 3.0 / 4.0

Aliro

FiRa

IEEE 802.15.4z

Security

Secure boot

signed firmware

key binding

anti-replay

Integration

BCM / door modules

multi-radio coexistence

UWB + BLE

Silicon

Qorvo QM33 / QM35

NXP

STMicroelectronics

Nordic (BLE Channel Sounding)

Case studies

A vehicle access system is secure ranging plus localization - the two disciplines needCode does best.

Qorvo: RF Leadership

Context: Rapid scaling for new chipset bring-up.

Scale: Grew from <10 to 30 FTEs.
Output: Supported bring-up of 9 new hardware platforms (SDKs, Drivers, Stacks).
Retention: Zero-churn core team retained for 5+ years.

Dedicated Development Center for RF Solutions

Bluetooth Mesh Smart Lighting Control System

Smart Lighting: Core R&D Extension

Context: Client needed deep, specialized expertise to pivot from proprietary tech to a new global standard.

Service: Deployed a dedicated squad of embedded engineers to function as the client's core R&D team.
Output: Co-authored official Bluetooth SIG protocols and delivered the world’s first certified BLE Mesh stack.
Value: Enabled the client to secure Series A funding and defined the industry standard for smart buildings.

Creative Werks: Innovation rescue

Context: Hardware obsolescence threatened production shutdown.

Action: Full-stack takeover (PCB redesign + Firmware + Mobile App).
ROI: 1230% ($1.6M value generated).
Speed: Payback period of 2–3 months.

NeedCode-case study - IoT Solution for Boat Lift Modernization - cover2s

PowerPollen: AgTech automation

Context: Lack of internal expertise stalled a critical automation project.

Action: Re-architected system using unified MCU and ISOBUS standards.
ROI: 13.8x ($2.9M value generated).
Impact: Enabled $1.9M increase in harvester value.

Strategic Partnership

needCode is an official business partner of Qorvo, bringing over 8 years of proven expertise and trusted service to the technology sector.

Check our performance

Members of the UWB Alliance

In 2025 we became a member of the UWB Alliance. This strategic step reinforces our commitment to pioneering Ultra-Wideband (UWB) technology.

Proudly Certified for Excellence and Security

needCode is officially certified for:
ISO 9001:2015 – Quality Management
ISO/IEC 27001:2022 – Information Security

ISO certifications reflect our focus on delivering reliable IoT solutions, smart product development, and secure technology services.

Testimonials

“I think the key takeaway from needCode is their ability to adapt and understand the customer's requirements. That took away probably a large portion of what could have been a lot of development time and expense for both companies.”

Bob Folkestad

President at Creative Werks

“One aspect that truly sets needCode apart is its profound expertise in firmware development. Their proficiency in various programming languages, embedded systems and hardware architecture is truly impressive. When faced with difficult problems, their strong problem-solving skills and analytical mindset shine through, allowing them to overcome obstacles with remarkable ease.”

Semeh Sarhan

CEO at Xtrava

“I worked with needCode while leading the NWTN-Berlin team in 2018. A big chunk for our FW development has been outsourced to them and they had proven to iterate very quickly, following specs and deliver on time. It was great working with them. I recommend working with needCode’s team on any Embedded SW development.”

Marco Salvioli Mariani

CTO at NWTN Berlin GmbH

“needCode Team proved to be one of the best engineers I have ever met. The part I like the most about the team is the more difficult an obstacle seems to be, the more motivated they were to find a solution and a way forward.”

Szymon Słupik

CTO at Silvair

“needCode is an outstanding partner. Their quick follow-up, scalability, and extensive professional network set them apart. Their expertise in wireless technologies has been valuable, supporting us from low-level drivers to architecture discussions.”

Tim Allemeersch

Director at Qorvo, Inc.

“needCode did a great job improving the firmware of the Vai Kai connected toys and developing new features, surpassing our expectations multiple times. I would definitely recommend hiring Bartek and needCode for the embedded software projects!”

Matas Petrikas

CEO & Co-founder at Vai Kai UG

Insights

Automating Bluetooth Qualification: From Weeks of PTS to an Overnight Job

There is a particular ritual in Bluetooth product development that anyone who has been through it remembers vividly. It is the manual qualification regression: sitting in front of a Windows machine running the Profile Tuning Suite, clicking through hundreds of test cases over the course of a week or two, interpreting results that range from […]

Documentation as a product: how good SDKs treat docs as code

The deliverable customers interact with most often is the one most commonly treated as a secondary artifact. Six document types, six audiences, and one release gate that fixes most of the failure modes. A semiconductor SDK can have an exemplary architecture, a thoughtfully versioned C API, a security framework that maps cleanly to PSA Certified […]

FAQ