The best everyday objects make their purpose obvious.
You pick them up. They do their job. You get on with your day.
We think consumer technology should feel just as natural. So we're working on physical utilities that meet a common need, do a useful job, and ask very little of the person using them.
The technology should handle the complexity. You should get the benefit.
There's more to simple.
A clear action.
→
v/h
→
A useful result.
A familiar control. A job done. On with your day.
→→→
↑Adjust as needed←
Work with what's happening.
The device's inputs give the agent information about the task and its surroundings. The agent uses that information to understand what needs doing.
Choose an appropriate action.
The agent works out what to do within the device's purpose and limits. The person using it should be able to focus on the result.
Do something useful.
The agent can use the device's tools, controls, or mechanisms to carry out the task. Its value comes from the work it helps complete.
Check the work.
The agent checks the result and can adjust its next action. The device should make it clear when the job is done or when someone needs to help.
Select a stage to look closer.
An agent under the hood. A useful object in your life.
Our approach puts an agent inside the device, where it can understand the task, act through the device's tools, and check its work.
The point is a better result with less effort from you. The intelligence has to earn its place.
The standard
Good to use. Good to own.
What we ask of everything we're building.
Familiar by design.
Useful in an ordinary day.
A recurring need, shared by many people. The kind of thing you reach for because it helps.
Simple from the start.
A clear purpose and understandable controls. Using it should feel natural, whatever your comfort with technology.
Capable on its own.
The core job should work locally. No app, account, subscription, or internet connection required.
Yours to depend on.
Each product should earn its own place in your life and keep doing its job without needing the rest of an ecosystem.
Living with it
Just turn it on.
The first interaction should feel familiar, even when the capability is new.
The familiarity of an ordinary light switch.
An object you own. A job it can do.
Start without setup.
Our aim is to let you use the core function without an account, a companion app, or pairing it with your phone.
Know where you stand.
You should understand when the task is complete and when something needs your attention. The device should explain the outcome in everyday terms.
Keep what you bought.
The computing needed for the job should live in the device. Continued use should come with ownership, without a subscription or a connection to a service.
A v/h utility has to be useful through ordinary, repeated use. The first product is still in development, and these are the questions guiding the work.
Need.
Would people reach for it?
The need has to be common and frequent enough to justify another object in someone's life. We start by looking at the work people already do.
Capability.
Does the agent help?
The intelligence has to improve the result, reduce the effort, or handle conditions a simpler approach cannot. Being new is only part of the work.
Trust.
Can you depend on it?
It needs to work beyond a carefully prepared demo. Price, upkeep, clear feedback, and reliability all belong in the same product decision.
A note from Vedh
v/h
I want to build something people simply want to have around.
Something with a clear purpose. Something that makes a small part of everyday life easier, and keeps doing it well.
That's the ambition behind v/h. We're at the beginning, developing our first utility. The product has to earn its place. This is the standard we're building towards.
We're at the beginning. Here's what we can say so far.
What is a consumer utility?
For us, it's a physical product with a clear, useful job that comes up in everyday life. Its purpose should be understandable to someone who has no interest in technology.
The ambition is a new capability that feels natural to use and deserves a place among the things people depend on.
Is v/h building one device that does everything?
We're looking for a focused job with a broadly shared need. A product can help many people without trying to do everything.
Over time, we'd like to build a family of utilities. Each one should be useful on its own.
Will I need to talk to an AI?
Our goal is an understandable set of controls tied to the task. Writing prompts, choosing a model, and managing the agent should not be part of the owner's job.
The agent belongs inside the product, where it can help do the work.
Why does local operation matter?
We want the core capability to be part of the object you buy. It should work without an internet connection or an ongoing subscription.
Keeping computation in the device can also reduce the need to send personal information elsewhere. Protecting that information still requires careful engineering.
What is the first product, and when can I get it?
We haven't announced a product, a price, or a release date. We're developing the first utility around the principles on this page.
The familiar objects photographed here are references for simplicity and usefulness. They are not v/h products.
