Skip to content
Plazoleta
Get in touch

Everything we build stands on open source. Giving back is only fair.

Open Source

Every project we deliver stands on hundreds of libraries, frameworks and tools somebody published for free. Without that anonymous work there would be no Plazoleta: charging for closed software while giving nothing back would show, at the very least, a bad memory.

So part of our time goes into tools we publish and maintain ourselves, under the MIT licence, with public docs and open issues. They aren't marketing or demos: they're software we use daily, which anyone can audit, fork and improve.

Publishing forces better work. Code that knows it will be read gets written more carefully, documented and tested — and that comes back to client projects as craft.

Tell us about your project

What you get

  • Tools we use ourselves first

    We don't publish abandoned experiments: FlupCode and OpenGit come from our own needs —driving coding agents and understanding large repositories— and they're maintained because we use them every day.

  • MIT licence and a genuinely open repo

    Code, roadmap, decisions (ADRs) and a ticketed backlog, all public. No open-washing: if it says MIT, it's MIT.

  • Maintenance with judgement

    Green CI, versioned releases and issues that get answered. Opening a repo is easy; keeping it alive isn't — and that's what we commit to.

Don't take our word for it

Our own product, in production. Try it and judge for yourself.

FlupCode

flupcode.com/

A Claude Code–style web and desktop cockpit for OpenCode, with the engine untouched.

  • · Web and desktop on top of the OpenCode engine, untouched: it speaks the same HTTP + SSE API as the terminal TUI
  • · Rich chat with side-by-side diffs, a real embedded terminal and per-session permission modes, from Manual to Bypass
  • · Usage dashboard with sessions, tokens and an activity heatmap; remote control from your phone via QR, end-to-end encrypted

OpenGit

github.com/rldona/OpenGit

A desktop Git client for Windows, macOS and Linux, with SourceTree-style readability and genuinely open code.

  • · Canvas commit graph with incremental loading: smooth in repositories with tens of thousands of commits
  • · Hunk, line and selection staging without leaving the app, with history operations —merge, cherry-pick, revert and interactive rebase with a preview—
  • · Tauri 2 + React with the system git binary as the single source of truth: Git is orchestrated, never reimplemented; MIT, with installers for all three platforms in Releases

When we're not for you

  • If you're after a tool with 24/7 support and a signed SLA. Open source is maintained with care, but without a contract behind it there are no timing guarantees.

  • If you need your company to set the roadmap. We listen to proposals, but the direction follows what the tool needs, not a sponsorship.

  • If what you want is to «do open source» as an image campaign with no maintenance afterwards. Publishing and abandoning does more harm than never publishing.

If you recognise yourself here, tell us anyway. I'd rather point you somewhere else in an email than have us both find out halfway through the project.

Questions

Why does a small studio spend time on open source?
Because we live off it, and because it makes us better: open code gets read, criticised and improved in public, and that discipline feeds back into every client project. It's also the one proof nobody can argue with: real, open software you can build right now.
Can we use your tools in our company?
Yes: MIT licence — use, modify and distribute them without asking. If you find a bug or miss something, open an issue — and if you'd like to contribute, the repo's CONTRIBUTING explains how.

Other services