Skip to content
Plazoleta
Get in touch
Software engineering studio

Custom software.We build itwith you.

We're a small studio with more than 15 years building software. We develop web apps, mobile apps and AI solutions for small businesses and product teams. We work with you from start to finish, shipping every two weeks, and you always talk to the person writing the code.

Tell us about your projectSee what we do
  • 5products in production
  • 15+ yearsof craft on the team
  • <24hto reply to your project
01Services

What we do, and what we don't.

We only list what we can stand behind, and we organise it by the problem it solves rather than by the technology. If your project doesn't fit here, we'll tell you and save you the meeting.

02Cases

Problem, solution and outcome.

The interesting part of a project isn't the screenshot: it's what was broken, what we built and what changed. The ones marked as our own product are exactly that: nobody commissioned them, which is why we can show the inside of work a client wouldn't always let us describe.

19,560forecasts verified
Our own product · Weather

Isobaria: publishing how wrong your own product is

isobaria.com
Problem
Weather apps give you a number and keep quiet about the margin. When the models disagree with each other —which is exactly when the forecast is worth least— you never find out: you see the same figure with the same confidence.
Solution
Isobaria cross-references three models (ECMWF IFS, ICON and GFS) into an agreement index that drops when they disagree, and publishes a verification page with each model's measured error. When the first independent validation against AEMET weather stations qualified the earlier method, it was published anyway, with its limitations spelled out.
Outcome
The June 2026 verification compared 19,560 forecast-observation pairs across eleven official stations, with the evidence archived immutably and the breakdown by model, horizon and province open to anyone. The product can be audited from the outside, which is the opposite of what the sector does.
  • Next.js
  • TypeScript
  • Open-Meteo
  • AEMET
100%of the trip, offline
Our own product · Travel

Jornia: a trip planner that works in airplane mode

jornia.app
Problem
Travel apps ask for an account and a connection precisely when you have neither: in a foreign airport, with no data and the gate changed. And your bookings —name, reference, flight— end up on somebody else's server.
Solution
Offline-first not as a checkbox but as the data model: the whole itinerary lives on the device, the map downloads by area, and the boarding pass is scanned entirely on the phone. None of it needs an account, and none of it leaves the handset.
Outcome
In the July 2026 comparison against Tripsy, TripIt and Wanderlog, the features they keep behind a paid tier or solve on a server —offline boarding pass and offline map— are here with no account, and verified in airplane mode.
  • Kotlin
  • Jetpack Compose
  • Material 3
  • Mapbox
100+editions sold
Handmade publishing

Carmela Cartonera, a publisher selling books made by hand

carmelacartonera.com
Problem
Carmela Cartonera sells handmade editions of works it also gives away as PDF and EPUB. They needed to sell online without looking like a generic ecommerce, with no technical team to maintain a shop, and with handmade production that can't cope with large volumes.
Solution
A very fast static site with a single dynamic point —payment—: catalogue and free downloads versioned in the repository itself, no CMS and no database, and Stripe checkout without user accounts. A real photograph of each copy is the centre of the page, not a decoration.
Outcome
More than 100 handmade editions sold, with a catalogue maintained straight from the repository and no CMS or database cost: publishing a new work is a commit.
  • Next.js
  • Tailwind CSS
  • MDX
  • Stripe
  • Vercel

Trusted by

03Our own products

Don't take our word for it: download it.

We build and maintain our own products in production —apps on Google Play, open source packages, this very site—. Nobody commissioned them and nobody reviews them: whether they're well or badly built is on us.

Plazoleta

plazoleta.dev

This very site: our calling card, built from scratch.

  • You're looking at it: server-rendered with Next.js, no template and no visual page builder
  • All the content lives typed in a single file — no CMS, no admin panel behind it
  • Our own design with Space Grotesk; zero stock components

Isobaria

isobaria.com

Weather from three models at once, with a public scorecard of how wrong each one is — nothing hidden.

  • Cross-references ECMWF IFS, ICON and GFS —served by Open-Meteo— into a model-agreement index that drops when they disagree, not when they fail
  • Public verification against the ERA5 reanalysis at /es/verificacion: 2,452,800 hours measured across 20 locations, with each model's error in plain sight
  • Covers all 8,128 Spanish municipalities, with RainViewer radar and official AEMET warnings shown in their literal wording, never reworded
  • Next.js with pages regenerated every 15 minutes; no accounts, no identifiers, aggregate usage measurement only (RUM)

LoverCast

lovercast.app

IPTV player and organiser for Android and Android TV.

  • One codebase for phone and Android TV, with two ways of being used
  • Real-time sync across devices: start on your phone, carry on watching on the TV
  • Metadata enrichment from external sources, plus offline downloads
  • Payments and multi-device licensing with Stripe

Jornia

jornia.app

A native Android trip planner.

  • Native Android with Material You, not a cross-platform port
  • Offline-first architecture: the whole itinerary lives on the device
  • Home screen widgets

aemet-mcp

www.npmjs.com/package/@rldona/aemet-mcp

Giving AI the Spanish met office's forecasts. An open source MCP server, on npm and in production.

  • Connects AEMET's official meteorology to MCP-compatible AI assistants and agents, such as Claude
  • Already in production: it powers isobaria.com through Next.js API routes on top of the library
  • Genuinely open source: published to npm with provenance and OIDC, public repo, green CI and versioned docs

You can open and check every bit of this. Shall we talk about yours?

Tell us about your project
04Technologies

The problem first. The technology second.

We choose the stack that best fits your product, your team and your timeframes. Never the other way round.

Frontend

  • React
  • Next.js
  • TypeScript

Mobile

  • iOS
  • Android
  • React Native

Backend

  • Node
  • Python

Cloud

  • AWS
  • Azure
  • Vercel
  • Docker
  • Terraform

Data

  • PostgreSQL
  • Redis

AI

  • OpenAI
  • Claude
  • RAG
  • MCP
05How we work

From idea to production, without waiting until the end.

We build and ship from the start, with progress every two weeks. And we carry on after launch.

  1. 01

    Discovery

    We look at the business problem before the technical solution. We come out with scope, risks and an estimate you can rely on.

  2. 02

    Design

    Architecture and UX in parallel. We define how it will be built and how it will be used, and validate that before writing code.

  3. 03

    Development

    Short iterations with continuous delivery. You see working software every two weeks, not progress reports.

  4. 04

    Launch

    Going live with automated deployment, observability and a contingency plan from day one.

  5. 05

    Evolution

    Support and ongoing development. The product keeps growing with your business instead of ageing.

The full method, in writing
06Why us

Being small isn't a limitation, it's the advantage.

We don't compete on size or on catalogue. We compete on you working directly with people who know the craft — and on being able to check that from the first call.

  • You talk to whoever builds it

    No account managers, no rotating juniors. The person listening to you is the one writing the code.

  • New company, old craft

    More than fifteen years each building software in production. The studio is young; we aren't.

  • Few projects at a time

    That's why we can properly get into yours. If we're not a fit, or we can't make it, we say so before starting.

  • We hand over, we don't lock you in

    Code, infrastructure and documentation your team can maintain without us. Staying is up to you.

  • Accessibility, performance and security as standard

    Requirements from the first commit, not a phase that gets cut when deadlines bite.

No middlemen and no rotating juniors: you talk to whoever builds it.

Tell us about your project
07Team

The people you'll be talking to.

No account managers in between. Whoever listens to you on the first call is the one who'll write the code, and their track record can be checked.

Portrait of Raúl López

Raúl López

Software engineer and founder

More than 15 years building software. I work across product, architecture and code, helping turn ideas into digital products that actually work. At Plazoleta I'd rather work directly with whoever has the problem and build the solution together.

Portrait of Macarena López Chamorro

Macarena López Chamorro

International Projects Lead

I lead the international side of Plazoleta's projects, connecting clients, teams and opportunities across borders. From the first conversation to delivery, I bring a global perspective to every project and keep collaboration clear, smooth and close.

Portrait of Tarek Homsy

Tarek Homsy

Business Development Lead

I lead client partnerships at Plazoleta, connecting businesses with the technology solutions that best fit their needs. I manage the commercial relationship from the first conversation through to long-term collaboration, helping turn ideas and challenges into successful projects.

08Contact

Tell us about your project.

Within 24 hours we'll look at your idea and suggest the best way forward. No commitment, and you'll be talking to whoever would build it.

Email
hello@plazoleta.dev
Where
Madrid, Spain
Book 15 minutes

No prep, no commitment: tell us what you need and we'll tell you whether we can help.