Build with VibeOnChip
Let’s find something useful to build.
Have a device, an API or a developer tool? I’m Niclas. I use AI to develop software and firmware, test ideas on real hardware and turn what I learn into demos people can understand.
Independent builder · QA background · Mantorp, Sweden
A starting point, not a fixed package
Bring a product and a question. We’ll choose one useful direction and agree what a good result looks like.
Hardware & devices
A display, development board, sensor or connected device. Explore a practical use case with software or firmware, then try it on the actual hardware.
For example: could your display make an AI workflow easier to follow?
AI platforms, APIs & developer tools
Connect your tool to a small application or physical interface. Explore what its API or SDK enables and find the friction a builder encounters along the way.
For example: what could someone build with your API beyond a chat window?
Demos & documented prototypes
Take one idea far enough to demonstrate, test and explain. A focused prototype can help your team assess a direction or show developers where to start.
For example: a working demo, a build walkthrough and the next questions to investigate.
Useful work. Clear handover.
We agree the deliverables before starting. Depending on the project, that can include:
Publication, source access, licensing, ownership and media reuse are agreed together. Hardware or AI credits can support development; commercial work is scoped separately.
From an idea to a build you can inspect
VibePulse brings Claude Code and Codex usage, reset times and agent activity to a dedicated display. The firmware, companion software and setup guides are public under the MIT license.
Waveshare supplied hardware for development and testing. That support gives me devices to build with, check and document. Features and verification still vary by model.
Development hardware supplied by Waveshare. The builds, tests and documentation shown here are VibeOnChip’s own work.
You work directly with me
I founded VibeOnChip in 2026 in Mantorp, Sweden. My background is in QA and testing. I use tools including Claude Code and Codex to help develop software and firmware, then take the work back to the device.
I choose the use case, direct the build, test the result and explain what happened. That includes the parts that need another attempt.
From first message to next decision
Send a product link, the use case you’re curious about and any useful docs, API or SDK information.
We check feasibility, choose the outcome and agree resources, timing, commercial terms and what can be shared.
I develop and test the agreed prototype. You get the checkpoints we agreed on, including limitations and open questions.
We look at the result and decide whether to refine it, share it, explore another direction or stop there.
Before we start
Yes, let’s discuss the product first. We’ll agree suitability, shipping, any return arrangements and what work is in scope before you send it. A hardware sample doesn’t automatically include a review or a development project.
No. Displays are where much of the current work is, but I’m interested in other devices, APIs and developer tools. Share what you have and what you want to explore; we’ll check access, documentation and feasibility first.
It can take different forms. A focused project can have a commercial scope. Hardware, development access or AI credits can support exploration. We agree expectations and any public disclosure up front.
We agree source access, ownership, licensing, publication and reuse rights before building. VibePulse’s existing MIT license doesn’t automatically apply to a new collaboration. Private prototypes and public builds are both topics to discuss.
Only if that is part of our agreement. We decide what may be shown and when. The outcome is reported honestly; a positive recommendation, audience reach or sales result is not guaranteed.
A prototype helps answer a defined question. It isn’t a product certification or a promise of production readiness. The handover should make the tested setup, known limits and further work clear.
Have something in mind?
Tell me what it is, what you’d like to explore and what a useful result would be. A short first message is enough.
A helpful first message
Opens an email draft with these prompts. Send it when you’re ready.
Please share documentation links, not passwords or API keys.