CSS and HTML code on screen during website development

What we build with, and why we pick each piece

We don’t defend any technology out of preference. Every project has a right answer, and it depends on your catalogue, your team, and who maintains this in two years.

  • Frontend
  • Backend
  • CMS and ecommerce
  • Automation
  • Infrastructure

Technology is chosen for the problem, not the trend

There’s an obvious temptation in this trade: always use the same thing, because it’s what you know, and convince the client it’s what they need. Comfortable for the agency, expensive for whoever pays.

We work across a wide range precisely so we can say no. If your five-page site doesn’t need React, we’ll tell you. And if your three-thousand-SKU store with ERP integration won’t fit a marketplace template, we’ll tell you that too.

We choose with data, not intuition

These figures genuinely shape what’s worth learning and what’s worth recommending to you.

75%
of analysed Spanish online stores run on WooCommerce, against 16% PrestaShop and 7% Shopify

The Art of Ecommerce, analysis of 54,651 Spanish stores, 2026

61.9%
of developers use HTML and CSS daily — still the foundation of absolutely everything

Stack Overflow Developer Survey 2025

18.9%
use PHP, a figure that misleads: it powers WordPress, WooCommerce and PrestaShop, which is most of Spanish ecommerce

Stack Overflow Developer Survey 2025

The full stack

Grouped by role. Hover any logo to see what we use it for.

Languages and standards

The foundation everything else sits on. Get this wrong and no framework saves you.

  • HTML5Semantic markup — literally what Google reads
  • CSSResponsive design without leaning on templates
  • JavaScriptInteractivity, measured so it never costs you load time
  • TypeScriptJavaScript with types: fewer production bugs
  • PHPWhat powers WordPress, WooCommerce and PrestaShop underneath
  • PythonData scripts, integrations and automation

Frontend

What your customer sees and touches. Chosen per project: not everything needs a framework.

  • ReactComplex interfaces and web applications
  • Next.jsServer rendering when SEO leads
  • Vue.jsA lighter option for panels and widgets
  • AstroContent sites that load almost instantly
  • Tailwind CSSA consistent design system with no dead CSS
  • SassMaintainable CSS on larger projects
  • BootstrapWhen maintaining something already built on it
  • ViteFast builds and small bundles

Backend and databases

Where your data lives. The part nobody notices until it breaks.

  • Node.jsAPIs and services in JavaScript
  • LaravelCustom PHP applications with proper structure
  • SymfonyThe framework PrestaShop runs on
  • MySQLThe database behind almost all shared hosting
  • MariaDBMySQL-compatible, common on modern servers
  • PostgreSQLWhen the data and the queries get serious
  • MongoDBData without a fixed schema
  • RedisCaching, so heavy pages fly
  • GraphQLAPIs that return exactly what you ask for

CMS and ecommerce

The platforms behind 97% of Spanish online stores.

  • WordPressThe most widely used CMS in the world
  • WooCommerceEcommerce on WordPress, with no per-sale cut
  • ShopifyFully managed: you sell, you administer nothing
  • PrestaShopLarge catalogues, multi-language and B2B
  • ElementorVisual editing when the client prefers it
  • StripeOnline payments and subscriptions

Marketing and analytics

Without measurement there is no optimisation — only opinions about spending your money.

  • Google AdsReaching people with buying intent
  • Google AnalyticsWhich pages bring customers and which earn nothing
  • Search ConsoleWhat people search before they find you
  • Tag ManagerTracking without touching code every time
  • Meta AdsFacebook and Instagram to create demand
  • TikTok AdsShort video for younger audiences

Automation and AI

Standard tools, not black boxes of ours: if you leave, the flow is still yours.

  • n8nAutomations hosted wherever you choose
  • MakeVisual flows across hundreds of apps
  • ZapierQuick connections for simple cases
  • ClaudeDrafting, classifying and summarising, with human review
  • AirtableA database non-technical teams can actually use
  • NotionShared documentation and processes

Infrastructure and tooling

What makes a project maintainable in two years, not just deliverable today.

  • GitVersion control: nothing is ever lost
  • GitHubRepository in your name and automated deploys
  • DockerIdentical environments in development and production
  • CloudflareCDN, security and global speed
  • VercelDeployment for modern applications
  • FigmaDesign and prototyping before a line of code

How we decide on each project

Four questions we settle before writing a line of code.

Who will maintain this?

If your team isn’t technical, an undocumented custom build is a time bomb. Sometimes the right answer is the boring platform anyone can work on.

How much will it grow?

Forty products and four thousand are not the same problem. We size for what you’ll have in two years, not just today.

What must it talk to?

If an ERP, POS or CRM is involved, integration capability outweighs every other technical consideration.

What if we leave?

We pick standard, documented technologies. If you ever want to change supplier, you must be able to without rebuilding everything.

Full stack means the conversation never breaks

When the frontend, the backend, the database and the integrations are handled by the same people, the classic problem disappears: nobody passes the buck, and design decisions already account for what the server can take.

It also means we can join other people’s projects midway. We audit the code, tell you honestly what state it’s in, and whether continuing or rebuilding makes more sense.

  • From design to deployment

    One conversation from prototype to production.

  • No translation layers

    What you discuss with us is what gets built.

  • Your code, documented

    Repository in your name from the first commit.

Developer working on the code of a custom web project

Technology FAQs

Why WordPress on some projects and custom on others?

Because they solve different problems. WordPress gives you a proven CMS that’s cheap to maintain and your team understands. A custom build gives you exactly your operation, but costs more and depends on someone maintaining it. The question isn’t which is better, but what your case needs.

Isn’t PHP outdated?

That’s a widespread and fairly unfair idea. Modern PHP with Laravel is fast and pleasant to work in, and above all it powers WordPress, WooCommerce and PrestaShop. Giving up PHP in Spain means giving up most of the real ecommerce market.

Do you build mobile apps?

We build web applications that work properly on mobile and can be installed like an app. For native store apps we’re clear about when it pays off and when it’s spend you won’t recover — and we’ll say so before taking the project.

My project uses a technology you don’t list — can you maintain it?

Tell us about it. If it’s reasonably standard, almost certainly yes. We start by reviewing the code to assess its state before committing to anything.

Which technology does your project need?

Tell us what you want to build and we’ll tell you what we’d use and why.