A companion shouldn't live in one device.
InspireLog is an iOS app today. But the premise — something that knows you, remembers, and shows up at the right moment — gets more true the closer it sits to your actual life, and your actual life is not happening on a phone screen.
This page is where we're honest about where we think this goes. None of what follows is shipping, and we have no integration API yet. It's published because the device makers we'd want to build with should be able to see how we're thinking before there's anything to sign.
On the wrist
A watch knows when you moved, when you slept, when your heart rate spiked before a meeting you said you were fine about. That is context InspireLog could reflect back — not as a dashboard of numbers, but as a nudge that arrives at the moment it matters.
Cameras and eyewear
Camera-equipped wearables see what you see. The opportunity is a companion that remembers the room, the whiteboard, the person you met — without you narrating it. The hard part is doing that in a way people actually trust, which is why this is research and not a roadmap item.
Always-available audio
Earbuds and open-ear audio make a companion something you talk to rather than something you open. Voice is the most natural surface for a presence that is supposed to feel like a friend, not an app.
Ambient and in-car
The moments worth reflecting on rarely happen while you are holding a phone. Displays and speakers you pass by — at home, in a car — are where an ambient companion stops being something you check.
What we won't trade away
More sensors means more ways to get this wrong. These are the constraints we'd hold any hardware partnership to — including ones that would be commercially attractive without them.
Consent is the feature, not the setting
Any sensor we support has to be something a person switches on deliberately, understands the scope of, and can revoke in one step. A companion that quietly widens its own access is not a companion.
Keep what we can on the device
We would rather process on-device and send less than build a pipeline that vacuums raw sensor data to a server because it is easier. This constrains what we can ship, and we think that is correct.
Partners own their users
We are not looking to sit between a device maker and the people who bought their hardware. The interesting version of this is InspireLog making your device more valuable to its owner.
Building hardware that should know its owner?
We'd rather talk to device makers early — while the integration surface is still a conversation instead of a spec. If any of the above is close to what you're building, tell us what you have in mind.
Talk to us about hardwareNo SDK, no API, no partner program yet — just the founders and an inbox.