Software engineering · Argentina and the world

One idea.Every screen.

We build high-quality software for any platform: websites, apps, touch kiosks, games and technology innovation. With engineering rigor, editorial design and results you can measure.

  • Performance

    Measured on every delivery, not promised.

  • Security

    From day one, not at the end.

  • Our own code

    No templates, no shortcuts.

  • Three languages

    Spanish, English and Portuguese.

02 — What we build

One engineering standard for every platform.

We pick the technology for your product and your audience, not for what we already know how to use. The result is the same quality in a website, an app, a kiosk or a game.

  • 01

    Websites and web platforms

    Fast, secure and built to rank. Every page loads instantly and is made to turn visits into inquiries.

    SSR · Technical SEO · Multilingual

  • 02

    Mobile apps

    One codebase for iOS and Android, with secure sessions, notifications and offline use. Built for the real world: patchy signal and modest devices.

    iOS · Android · Flutter · Dart

  • 03

    Touch kiosks

    Interactive experiences for fairs, shops and public spaces: full screen, multi-touch and ready to run all day.

    Multi-touch · Full screen · Automatic start

  • 04

    Games and interactive experiences

    2D, 3D and virtual reality games, with stable frame rates on the target device and game feel as the priority.

    Flutter · Dart · Unity · VR

  • 05

    Custom software and APIs

    Management systems, integrations and APIs designed around your operation, not a template. Secure data, ready to grow.

    Go · PostgreSQL · Rust

  • 06

    Technology innovation

    Prototypes and applied research: we take a new technology and turn it into a product that works and can be measured.

    Prototypes · R&D · Proofs of concept

Hardware and software

One engineering standard, from the screen to the device.

We design the software and the experience of touch kiosks for fairs, shops and public spaces: from the interface to automatic start on the device.

03 — How we work

Four steps. Each one with its proof.

  1. 01

    Understand

    Before drawing anything, we listen and measure: what real problem exists, who uses it and what success looks like.

    ProofA one-page brief that you approve.

  2. 02

    Design

    We prototype the whole experience, including the states almost nobody shows: empty, error and offline.

    ProofA clickable prototype before any code is written.

  3. 03

    Build

    Our own code, reviewed and tested, on an architecture that scales without being rewritten.

    ProofIncremental deliveries you can use and evaluate.

  4. 04

    Measure

    We launch with real metrics —speed, stability, conversion— and keep refining with data.

    ProofA report with numbers, not adjectives.

04 — Work

Software in production, with the numbers in plain sight.

We show real sites before a gallery of promises. Every case includes the measurement of the published site.

Featured case · Digital newspaper

catamarcaya.com.ar

Google AdSense advertising without sacrificing speed.

CatamarcaYa is a digital newspaper with multiple Google AdSense ad slots. It is measured in PageSpeed Insights: speed, accessibility and SEO of the published site.

100

Mobile

100

Accessibility

100

SEO

Google AdSense

Ads

Sanicat Servicios

sanicatservicios.com

Public website for an environmental services and logistics company.

100

Mobile

100

Accessibility

Novamente

novamente.dev

Our own site is the first proof of the standard we offer.

100

Mobile

100

Accessibility

PageSpeed Insights · Lighthouse 13.6.0 · November 10, 2026

05 — Engineering

What lies underneath matters.

We choose tools for what they sustain over the long run, not for fashion. Every decision has its proof.

Frontend
Qwik with server-side rendering, always. PageSpeed 100 as a condition of delivery, not a goal.
Backend
Go and PostgreSQL with hand-written SQL: no layers hiding what actually happens.
Compute
Rust for heavy work, isolated from the rest and measured before it goes in.
Games and kiosks
Flutter, Dart and Unity, with performance measured on the target device, not the development machine.
Infrastructure
Our own servers, observability and deployments that are verified before they are considered done.

06 — Frequently asked questions

What people ask us before they start.

If your question isn't here, write to us and we'll answer with data.

See all the questions
How does a project start?

With a conversation. We listen, measure the starting point and put together a one-page brief with scope, timeline and budget in writing, which you approve before we begin.

How do you look after quality?

Every delivery has its proof: we measure speed, accessibility and stability on the real device and hand over a report with numbers. What could not be measured, we say so.

Which technologies do you use, and why?

We choose for what lasts, not for fashion: Qwik, TypeScript, Go, PostgreSQL, Rust, Flutter, Dart and Unity depending on the project.

How much does it cost and how long does it take?

It depends on the scope. After listening to you we put together a one-page brief, which you approve, with the scope, timeline and budget in writing before we begin.

07 — Let's talk

Tell us your idea. We take it to every screen.