Built for People, Not Profit

We create open source tools that don't cost anything to use. Transparent, accessible, and designed to actually work for you.

Active work

What we're building now

Flagship project

Active alpha

Nextcloud Native

One coherent, genuinely native workspace for your whole Nextcloud. The project is building toward a consistent experience across Files and the wider app ecosystem without embedding remote web pages.

Built with

  • Kotlin
  • Compose Multiplatform
  • Rust

Platform direction

  • Android
  • iOS
  • Linux
  • macOS
  • Windows
Project

Obiente Cloud

Infrastructure

A distributed platform for deploying and managing applications across multiple nodes.

  • Go
  • Vue
  • TypeScript
  • Docker

Uppe.

Monitoring

Distributed uptime monitoring built around independent, signed checks from multiple peers.

  • Astro
  • TypeScript
  • Rust

Obiente UI

Developer tools

A Vue 3 component system for accessible, themeable interfaces with shared foundations.

  • Vue
  • TypeScript
  • Tailwind CSS
  • Astro

About Obiente

We're a small team building open-source tools focused on filling people's needs, not our bank accounts.

What We Do

Unlike corporate companies, we want to prioritize our users rather than profits. We build software and tools that are completely free to use and powered by our community. From native clients and cloud infrastructure to distributed monitoring and UI components, our projects solve things we actually need without hidden costs or vendor lock-in.

Every tool we create is designed with transparency at its core. You can see exactly how it works, modify it for your needs, and contribute improvements back to the community. This isn't just about code, it's about building trust through openness.

Why We Started

"I got frustrated seeing so many tools that are way too expensive for what they offer. Built for maximum profit rather than to actually benefit the end user. They lock you in with minimal features and charge premium prices for basic functionality."

"That's why I started Obiente. We needed a better alternative to all the big corporate software that drains your wallet. Sure, there's usually a free option for everything, but they're often incomplete or missing key features. That's the gap I want to fill."

- Yaro Doornberg, Founder of Obiente

This frustration with overpriced, feature-limited tools led to Obiente's core mission: creating sustainable alternatives that actually serve users instead of shareholders. We've seen too many promising tools disappear or become inaccessible when companies pivot or get acquired.

Our goal is simple: build software that remains free and belongs to the people using it. Every project we create starts with something people need, not a market opportunity. That's how we ensure we're building things that actually matter.

Our Philosophy

We believe software should remain free, transparent, and accessible to everyone. We favor open formats, copyleft licensing, interoperability, and self-hosting so people can keep meaningful control over the software and data they depend on.

Our team brings together developers worldwide to build solutions that benefit everyone. We're not just creating software, we're building a community that drives innovation through shared knowledge. The principle behind every project remains the same: built for people, not profit.

The people behind Obiente

A small, distributed team combining product direction, engineering, and operations to keep the work moving.

veryCrunchy profile

veryCrunchy

Sets the direction for Obiente and works across product design, project planning, and full-stack development.

Founder & Executive Director

Espresso profile

Espresso

Coordinates the operational work behind the projects and helps turn ideas into sustainable day-to-day practice.

Chief Operations Officer

Grey_Stinger profile

Grey_Stinger

Builds and strengthens the backend foundations that support Obiente's software and services.

Back-End Developer

Data and privacy

Promises should be verifiable

Obiente projects serve different purposes, so their exact data needs are not identical. We start with the least data a feature reasonably needs and document exceptions instead of hiding them behind a broad promise.

Collect with a reason

Data collection should have a clear product purpose. If a service does not need information, the best default is not to collect it.

Keep choices visible

Controls should be understandable and available where they matter, with practical ways to view, manage, or remove data when supported.

Document the boundaries

Each project should explain what it stores, where information goes, and which external services are involved.

Design for independence

We favor interoperable and self-hostable approaches where they fit, so control does not depend on one hosted platform forever.

Read the commitments shared across Obiente services.

Read the complete data policy →