Getting startedCreate your first initiativeConnect version controlInvite your teamPlan today's work
Privacy PolicySecurityTerms of UseCSR PolicyContact
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Changelog
  • Docs

Features

  • Assistants
  • Workflows and agents
  • Capability management
  • Boards
  • Roadmap
  • Triage
  • Progress
  • Insights
  • CLI
  • Integrations

Solutions

  • Insurance
  • Finance
  • Software

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • Support
  • API reference
  • Desktop app
  • SDK
  • Vault
  • QR code generator
  • Video frame extractor

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXTikTokYouTubeMedium


Corporate Social Responsibility

We build the layer that lets teams hand work to AI agents. That makes a few questions our problem rather than someone else's: who answers for what an agent did, where the work runs, and whose hardware it runs on. This page is how we answer them.

Our mission

Build better work, not more work

People stay accountable

The models execute. One Horizon orchestrates. People remain accountable.

That ordering is the whole point. When a team delegates work to an agent, the responsibility doesn't move with the task. A workflow can stop and ask a person to decide, and what happened stays on the record afterwards: what ran, which model, what a reviewer approved.

We're not compliance software and we won't tell you we make your company compliant. What we do is make responsibility explicit instead of leaving it to whoever happened to be in the loop.

Technology ethics

You pick the intelligence. Workflows aren't welded to one vendor's model. Swap the agent underneath and your standards, review gates, and record stay put. A team that can change its mind about a model provider is in a better position than one that can't.

Privacy first. You control your own data. We don't run invasive monitoring, and we don't build features that turn a team into a surveillance target. Showing what work is happening is not the same as watching the people doing it, and we've kept that line on purpose.

AI you can question. Every AI-driven insight comes with what it was based on, so you can check the reasoning instead of taking the answer on faith. We audit our AI for fairness and bias.

Where the work runs

On hardware you already own. Agents can run locally against your own repositories and machines, as a first-class option rather than a fallback. A laptop that's already switched on does the work, instead of a server spun up somewhere else to do it for you. We believe that's the better trade for the footprint of AI-assisted work, and it's a large part of why we keep investing in local execution.

It matters for independence too. Teams that can run the work themselves aren't betting their delivery process on one foreign provider staying available, affordable, and agreeable.

In the EU by default. One Horizon's own product data stays in the EU. Executor data depends on the agent and provider you choose, which is your decision to make and ours to be straight about. The Privacy Policy sets out both paths.

Efficiently, where servers are involved. We audit our architecture for computational waste and act on what we find.

We haven't measured our total footprint, so take the case for local execution as reasoning rather than a number we can show you. We'd rather say that than publish an estimate dressed up as a result.

People first

We're remote-first across time zones, so work-life balance has to be designed in rather than hoped for. No daily commute, no paper, and travel only when being in a room genuinely changes the outcome.

We manage on trust, communicate openly, and pay fairly with equity for everyone on the team. We fund learning and development.

Community

What we publish. We write engineering and product articles on our blog, speak at conferences, and run workshops. If we learn something worth knowing, we'd rather write it up than keep it.

Where we talk. Our community Slack is open to anyone using One Horizon or thinking about it. Ask questions, tell us what's broken, or watch other teams work out how they want to delegate.

Where we meet. We host and take part in events with the Stripe Eindhoven community, mostly in person in Eindhoven. Anyone is welcome, including people who don't live here.

Who we hire. We hire inclusively and partner with organisations working on underrepresentation in technology.

Business practices

Pricing you can read. Clear prices up front, no hidden fees, no lock-in. Cancel whenever you like and your data is still yours.

Growth that doesn't cost quality. Customer feedback drives what we build. We'd rather take longer and keep the product good than ship fast and apologise.

We never sell customer data to third parties, and we never use it to train large language models.

Your data stays yours. You own it and you control it. We publish what we do with it in the Privacy Policy, and we run privacy and compliance reviews against that promise rather than assuming it holds.

Getting involved

Tell us where we're falling short, suggest something we should be doing, or work with us on sustainability and industry standards. Send us a message and it reaches a person.


PreviousTerms of UseNextContact

Contact

Contact One Horizon for legal questions, privacy requests, and data protection matters.

Privacy Policy

This Privacy Policy explains how One Horizon collects, uses, stores, and protects personal information.

Terms of Use

Review the terms that govern access to and use of the One Horizon platform.

Security

Review One Horizon security controls, EU hosting for the One Horizon control plane, encryption, access boundaries, and compliance posture.

  • Our mission
  • People stay accountable
  • Technology ethics
  • Where the work runs
  • People first
  • Community
  • Business practices
  • Getting involved
  • Back to top