About Javier Cañete and Jacar Systems

My first line of code was BASIC on a Spectrum 48k, at six years old. I have not stopped since. Cassette tapes, Linux kernels compiling at 3am on a Sunday, Perl 5, containers holding production through Friday evenings, and now technical direction at Jacar Systems. The tech changes every five years; the recurring question is always the same: what needs breaking and rebuilding this week so I do not stand still.

I work from inside the system, not from a slide deck. I have been on call at three in the morning, I have moved production on a Friday afternoon, and I have said 'no, that is a bad idea' when somebody had to. That is why calling me directly makes sense instead of a big consultancy: you talk to the person who will design it, and quite possibly to the person who will write the code.

I work in Spanish and English. Hardware, networking, operating systems, data structures, sound engineering practices, established patterns, fit-for-problem technology choices, architecture and methodology: all of it lands in the project from the first commit. Not a patch stitched on at the end.

Jacar Systems S.L. is the consultancy I run from Madrid. Since 2002 we have been putting infrastructure, software and product into production for Spanish SMBs. No franchise, no licence reselling, no empty slide decks.

The firm works across three pillars that can be hired separately or together depending on the problem: infrastructure and operations (cloud, on-prem, hybrid, observability, SRE), development and product (web, APIs, integrations, internal platforms), and applied AI and automation (agents, RAG, local LLMs, data governance).

One point of contact for the whole stack. SLAs against metrics you can see and code that stays in your repository. Zero black boxes.

We work in Spanish and English with public-sector and private clients in ERP, healthcare, retail, industry 4.0 and cloud-native architectures. The difference with a big consultancy is that the person picking up the phone is the one writing the code, and the person who wrote that code is still around six months later.