HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
luxonis
oak-hardware
HTML2020–2024
luxonis / oak-hardware

oak-hardware

Open Source OAK Hardware designs in Altium

2Distinct people
2Mentions
0Explicit recommenders
561GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open Source OAK Hardware designs in Altium

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year2 dated mentions

Observed mentions: 2020-07-08 14:41:12 UTC to 2024-09-17 02:59:16 UTC.

012020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

2 sources
Thank you, something to think about! $5000 to $6000 is a lot to swallow. I wish luxonis would get into some eye tracking hardware the OAK-D Pro seems so close to a monitor mounted eye tracking solution. https://www.luxonis.com/ https://github.com/luxonis/depthai-hardware/issues/114#issue... This does not fit my use case but seems like an interesting project. https://polar.sh/NativeSensors/posts/eyepather-new-tool-in-e... I feel like the field of eye tracking is entrenched so deep into research that it takes away from accessibility. It's not just the cost. Tobii is a good example where the hardware is capable but locks out accessibility from users so it doesn't cannibalize from sales from research/industry.
In Ask HN: Recommendations for Eye Tracking Hardware?
Thanks for the kind words. Brandon the founder here. :-) So although I could see how that quote could appear like that, the quote is not kissing the ring. We scoured the whole semiconductor start up scene to find a chip that could be used for this. There are only 2 chips (as I'm aware, as of this writing) that can be used in such a way: 1. Intel Movidius Myriad X 2. Inuitive NU4000AI. And the Inuitive, until super recently (i.e. 1.5 years after we have already built hardware off the Myriad X) was not ready to be used (had tape-out issues at the fab). So this made the Myriad X the only chip that (1) had the capabilities needed and (2) was actually available and in production. In terms of our open-source nature, the latter is what we've implemented - where we have closed source binaries running on the Myriad X - which then have a slew of
Read the rest
open-source counterparts on the host. Sorry if this came off disingenuous. Do you have advice on how to phrase it in a better way? https://github.com/luxonis/depthai-hardware - DepthAI hardware designs themselves. https://github.com/luxonis/depthai - Python Interface and Examples https://github.com/luxonis/depthai-api - C++ Core and C++ API https://github.com/luxonis/depthai-ml-training - Online AI/ML training leveraging Google Colab (so it’s free) https://github.com/luxonis/depthai-experiments - Experiments showing how to use DepthAI. The above includes open source hardware, core capabilities in C++ which can be cross-compiled for various hosts, and open-source training notebooks and use-case examples. So the goal of open-sourcing all that we can (including hardware) is to enable folks who have their own applications to leverage this, modify it, use it, etc. w/out having to even talk to us. We cannot open-source the code that runs on the Myriad X however, as then we wouldn't have a way to monetize, and would have to give up on the mission. (That, and we're also not allowed to.) Thoughts? Thanks, Brandon
In Luxonis wants to use computer vision to protect cyclists

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.