Skip to content
iMpact

We build software that respects the person using it.

iMpact is an independent technology company. We build software that respects the person using it.

Why we exist

Most software asks people to adapt to it. We started iMpact to work the other way round: to build tools that fit the way a person already thinks, and that stay honest about what they can and cannot do.

How we work

Small scope, long horizon. We prefer a product that does a few things dependably over a platform that promises everything. Decisions are written down, and unfinished work is described as unfinished.

What we are today

An independent company in its early stages, building ORION as its first product. There is no funding announcement, customer list, or award shelf to show — and we would rather leave those sections empty than invent them.

What we believe

Four commitments we design against.

  1. 01

    Useful before impressive

    We start from real work and real constraints. If a feature does not make a task shorter, clearer, or calmer, it does not ship.

  2. 02

    The person stays in command

    Software that acts on your behalf should show what it is doing, ask at the right moment, and stop the instant you say so.

  3. 03

    Restraint is a feature

    Fewer surfaces, clearer language, quieter interfaces. Depth is available when you want it, never demanded up front.

  4. 04

    Built to last

    We choose durable foundations over quick wins, and we would rather name what is unfinished than imply it is done.

Human control

Capable software should still answer to you.

Local first where it counts
Sensitive work should stay on your machine. Where a request must leave the device, ORION says so before it happens.
Permission, not assumption
Access to files, apps, and the network is granted per capability and revocable at any time, without hunting through settings.
No silent training
Your content is not used to train models. There is no hidden opt-in and no quiet change of terms.
Accessible by design
Keyboard, screen-reader, and voice paths are built alongside the visual interface, not retrofitted after launch.
Request early access