Verkada
Each of these is a real decision Verkada is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Verkada provides cloud-managed physical security and building-technology systems, combining hardware devices with a recurring cloud software platform. It serves businesses and institutions with distributed sites, such as enterprises, schools, healthcare organizations, banks, and government bodies. Its Command SaaS platform is the cloud software layer, and its command connector product turns any legacy camera into a cloud-native, AI-searchable node. Devices are provisioned and receive over-the-air firmware rollouts from the cloud, and a licensing layer turns the devices into a business.
Your first one is free. No card.
64 live right now.
The rest
Decide on the panel cutover before renewal window closes in 18 days
Some after-hours warehouse entries appear on video but leave no verified alarm record. You must weigh a hard cutover deadline against the risk of committing sites to an unproven response path.
Decide on a coverage warning instead of blocking setup of new sites
Newly added locations are generating avoidable daytime alarms before staff realize no schedule was set. You must weigh a clear warning against a stricter configuration path that could slow location setup.
Rank renewal risk before CSMs miss the accounts that need help
Renewal context is split between Salesforce and the camera platform, so risks can surface after the customer has already formed an opinion. You have to weigh earlier outreach against evidence a CSM can trust in a live customer conversation.
Group feedback on false alarms so repeat patterns show across sites
Recurring false-alarm complaints are arriving through different partner and ordering surfaces without a shared evidence trail. You must decide what the system groups, what product managers verify, and what stays out of roadmap evidence.
Route firmware findings before review queues bury the evidence
Firmware findings are being reopened because the evidence needed to judge them arrives in separate places. You must weigh faster routing against the human review needed to keep severity decisions defensible.
Surface technical risk before enterprise access plans harden
Security and network objections are appearing after customers request deployment plans. You must decide which evidence earns attention and which judgment stays with the Solutions Lead.
Trace OTA failures while the next camera release approaches
Post-OTA failures are being reopened because their device, storage, and release evidence does not agree. You must decide what AI assembles, what engineers verify, and how the team proves the workflow is trustworthy.
Rank causes of late events while engineers keep the release call
Late events leave security administrators with conflicting accounts of what a door did. You must decide what AI can assemble and what engineers must verify before acting.
Cut tracing of missed follow-ups to 30 minutes without blind guesses
Alarm records show the alert and response surface, but not why the expected follow-up disappeared. You must weigh faster release investigations against evidence engineers can trust before shipping.
Bring identity changes into access groups without spreadsheet weeks
University administrators spend up to 11 hours a week reconciling contractor and staff lists with access groups. You have to weigh faster proposed updates against reviewable control over who gets door access.
Prove revocation of credentials on 12 doors by day 14
Nineteen credential-lifecycle answers conflict across the bank's review materials for 214 doors. You have to weigh the branch launch date against controls that IT security can verify and sign.
Prove which fix clears the congested VLAN before Monday's clinic opening
Thirty-seven staff entries were delayed across two morning shifts at 46 doors. You have to weigh the fastest network change against the only maintenance window before patients arrive.
Set retention rules for search records so pilots skip legal review
Pilot organizations lack a consistent path to enable face and person search across their sites. You have to weigh faster investigations against controls privacy teams can defend locally.
Decide the camera expansion while export evidence conflicts
A federal camera expansion is paused because shipment and support records do not tell one clear compliance story. You have to weigh an opening-date commitment against a disposition that remains defensible after the cameras move.
Clear a camera shipment while procurement questions its TAA record
A public-sector camera shipment is paused because its origin record conflicts with the purchasing file. You have to weigh the installation deadline against a representation the evidence may not support.
Connect camera context to dispatch without widening video access
Campus dispatchers spend 4–7 minutes getting camera context during incident drills. You must weigh faster coordination against privacy limits on who receives video information.
Choose branch connectivity before construction locks the camera design
Five branches have conflicting LTE, bandwidth, and firewall evidence, while 640 cameras await a purchase order. You must weigh centralized investigation against a network boundary the CISO will not relax.
Stabilize camera access before the next hospital handoff
Twenty-seven cameras disappear from Command for up to 11 minutes at each shift change. You must weigh a fast DHCP correction against the hospital’s protected network boundaries.
Find the pattern in HIL failures after long alarm runs
Recurring communication failures are taking more than a day to classify across HIL evidence. You must weigh faster failure clustering against the review needed to trust a physical cause.
Choose a deep test of sensor runs instead of a connectivity screen
A 50-unit pilot must test dense wired sensor runs without adding more than six minutes per panel. You have to weigh fault coverage against line yield and build time.
Settle the panel build before the supplier starts the next lot
Some closely spaced wired-zone events disappear during high-density HIL runs. You must weigh supplier commitment against evidence that every intrusion signal reaches the console.
Stabilize power-recovery tests before release evidence goes stale
The HIL suite intermittently loses the expected alarm event after a console power interruption. You have to weigh realistic fault simulation against a release gate the team can trust.
Settle the cause of heat failures in DVT builds without auto-approval
Thermal failures are being reopened because test results and build notes point to different causes. You must weigh faster root-cause direction against the evidence an engineer needs to trust before changing hardware.
Power remote cameras through the night without pricing out coverage
Remote lots lose video when portable power is serviced or depleted. You must weigh overnight evidence continuity against thermal margin, serviceability, yield, and unit cost.
Choose an EMI path while nighttime detection is at risk
PVT cameras fail emissions checks and briefly lose detections when IR mode starts. You must weigh a tooling commitment against compliance margin, line yield, and usable nighttime evidence.
Stop IR resets while DVT boards near their build lock
Cold-chamber cameras restart when IR illumination turns on, putting nighttime footage at risk. You must weigh a fast board correction against thermal margin, supply availability, and DVT timing.
Correlate AW33 failures while DVT evidence still conflicts
AW33 units are failing EMI prescan, and the evidence points to competing physical causes. You must decide what AI can correlate safely and what engineers must verify before a build changes.
Prove the wireless path at each door so installers skip return trips
Installers are returning to doors that looked online when they were commissioned. You must weigh a useful field signal against added hardware cost and installation time.
Choose the surge path before production tooling locks
Powered wireless doors reset during building power tests while controller status remains online. You must weigh a durable enclosure change against the production date and an electrical mitigation.
Cool the controller before pilot tooling closes
Pilot controllers restart after hours of busy door traffic inside cabinets. You must weigh a fast enclosure change against manufacturability and validation evidence.
Decide how incident lessons are kept without exposing sensitive notes
Incident lessons disappear into local debriefs, leaving recurring camera gaps unmeasured. You must weigh a useful shared learning record against the sensitivity of incident details.
Choose alarm routing before 240 clinics copy a flawed policy
False dispatches account for 31% of after-hours alarms, yet guards have caught real perimeter events by overriding the system. You must weigh quieter routing against the risk of delaying a threat that only becomes clear after review.
Quiet loading alerts without losing perimeter threats
Scheduled deliveries now account for 46% of loading-area alerts, slowing review of genuine activity. You must weigh a quieter queue against the risk of suppressing a real perimeter event.
Trace role changes so access reviews stop rebuilding the story
Permission changes made through custom roles cannot always be reconstructed from the existing history. You have to weigh rapid delegated administration against evidence that holds up during an investigation.
Decide on AW33 release after a door keeps yesterday's schedule
A recovered wireless door may grant access under yesterday's schedule even after Command shows a new one. You have to weigh the launch window against evidence strong enough to protect occupied buildings.
Contain reboot loops before tonight's controller cohort
Three occupied sites have doors that briefly deny valid credentials after the overnight update. You must weigh rollout speed against evidence that the next cohort will stay available.
Build text search for footage without adding video to review
Security managers are manually reviewing footage when existing filters cannot express what they saw. You must weigh broader retrieval against the time and trust lost to weak results.
Set face-match thresholds before the old pipeline is removed
Nighttime face matches are rising, but security staff cannot confirm enough of them from the footage. You must weigh broader retrieval against the trust required for an irreversible cutover.
Quiet cart alerts while keeping unattended objects visible
Loading-entrance cameras send 31% of their alerts for routine delivery carts. You must weigh quieter alert queues against preserving detection of a genuinely unattended object.
Open mixed-camera deals without conceding the expansion
Partners are losing legacy-camera opportunities to alternatives that avoid hardware replacement. You must weigh a lower-friction entry point against a motion that still earns future camera expansion.
Close 18 sites before capital money lapses and renewal costs surface
The consortium could lose funding for 620 replacement cameras in 16 days. You have to weigh a closeable reseller structure against terms finance can defend beyond year one.
Package courthouse cameras before the reseller price expires
A county has paused a three-site camera order because the proposal makes licensing look like an added cost. You must weigh a fast, comparable commercial package against assumptions IT and procurement will defend.
Prove camera value when renewal costs reach the executive review
Six renewal customers are questioning license costs without a shared measure of investigation value. You have to weigh a repeatable programme against each customer’s distinct security and IT reality.
Choose a camera rollout both Security and IT accept in 12 days
Two emergency departments have coverage gaps, and six sites disagree on whether their networks can support expansion. You must weigh faster security coverage against an architecture IT will approve and operate.
Align campus cameras before the expansion order expires
Three campuses cannot release their camera expansion because their bandwidth estimates conflict. You have to weigh coverage needs against the network capacity IT will actually approve.
Prove exported footage is authentic when investigators ask
Security managers cannot independently verify that an exported clip still matches the camera-captured evidence. You must weigh a useful evidence check against the security boundaries around device and backend signing authority.
Choose an update control while urgent fixes face an integrity gap
Some cameras accepted update requests whose authorization cannot be fully reconstructed after recovery. You must weigh a fleet-wide update pause against a narrowly enforced control that still delivers urgent fixes.
Align firmware checks while a camera update waits
One signed firmware package passes one release check and fails another, holding the scheduled update. You have to restore a single trust decision without loosening the protection cameras rely on.
Show outage readiness for each site while the flag limits its claims
Security managers cannot tell whether an online camera is ready to retain video through an outage. You must weigh a useful fleet signal against claims the available device data cannot support.
Choose encoder settings before outage footage rolls off
Affected cameras are overwriting footage before the configured retention window after network outages. You must weigh evidence retention against playback reliability and storage wear before the OTA window closes.
Speed up live view while recording stays protected
Affected H.265 camera sessions take 8.4 seconds to show a first frame. You must weigh faster browser playback against camera CPU headroom and recording continuity.
Move sites in phases without losing control of access schedules
Mixed-estate customers are delaying cloud access deployments because no one can agree on the first site. You have to weigh a reusable programme against the local network and governance differences that determine whether customers commit.
Win security approval while four branches cannot meet the network design
Four branches cannot clear security review, putting 240 doors and $180,000 in guard costs at risk. You must weigh a fixed opening date against an architecture the CISO can defend.
Win approval of the network design so 180 badges work by Friday
One hundred eighty staff credentials are waiting on network approval, leaving new clinics reliant on temporary keys. You have to weigh an opening-day commitment against the customer’s VLAN and firewall standards.
Prove alarm recovery before installers hand over retrofitted sites
A panel can look healthy after power work even when an open door may not report. You have to weigh a credible recovery check against the time and friction added to installation.
Decide whether the firmware ships without hiding a second intrusion
Pilot sites are seeing duplicate incidents after reconnects, and some later door openings never arrive. You must weigh rollout timing against evidence that the next real intrusion will still escalate.
Prove a panel reports an open door after an outage before release
An open door can remain unreported after a brief panel outage, even when the panel reconnects. You have to weigh release momentum against proof that recovery still protects the site.
Turn sensor health into a readiness view while alarm handling stays fast
Security managers cannot see whether sensor and camera coverage supports verified response until an alarm arrives. You must weigh a useful readiness signal against the risk of distracting from urgent alarm handling.
Stop dispatch on stale video while real intrusions still escalate
Fourteen of every 10,000 verified alarms are reaching emergency dispatch after later video evidence changes the picture. You must weigh faster escalation for real intrusions against a one-way workflow change that could delay them.
Shorten the alarm path to video while keeping event order intact
Only 71% of wired-zone alarms show live video within three seconds, leaving operators to wait during an intrusion review. You have to weigh a faster event path against duplicate alerts and reliable sensor health signals.
Preview wireless-lock readiness before staff depend on new doors
Wireless-lock sites can appear online even when their intended access policies have not been tested against real connectivity conditions. You have to weigh a useful pre-activation signal against the risk of overstating what the data can prove.
Choose an update path in seven days without stranding offline sites
A controller trust-path concern must be addressed within seven days across occupied sites. You must weigh stronger remote protection against the chance of disrupting reliable door access.
Fix the online state of a lock once its mobile credentials fail
Two sites show doors as online even after mobile credentials fail at the lock. You must weigh faster fault detection against noisy offline alerts during normal connectivity loss.