Our story
Foxcub was born from the shared ambition of two partners to create, in 2016, a company dedicated to helping organisations work more innovatively and efficiently with their data. Our origins lie in a common pursuit of innovation, data expertise, and team fulfilment in day-to-day work.
Julien Homo
CEO – Data Architect
Kévin Darty
CTO – Data Architect
RESPONSIBLE DATA AND AI, BY DESIGN
We design systems so control stays with the data holder. Data can remain where it is, while access rights and conditions of use travel with every exchange. A withdrawal propagates across the full processing chain rather than stopping at its point of origin. This makes data sovereignty an operational property, not a declaration.
We build trustworthy AI around evidence, not plausible output. Every answer points back to its supporting sources, with provenance and use recorded throughout the chain. When evidence is insufficient, the system abstains. Compliance with European rules on AI, copyright and personal data is treated as an architectural requirement from the start.
We favour open and reusable data whenever conditions allow, guided by FAIR principles and open standards. We choose models sized to the task instead of defaulting to the largest available option. Resource use is measured across design and operation so choices can be compared and adjusted. Openness and measured efficiency become design constraints, not afterthoughts.
Open, sovereign and frugal in practice
These commitments guide our daily technical choices, from component selection to hosting and operations. They give organisations durable control over what they build, how it evolves and what it consumes.
Open by default
We begin with open-source components and open standards, then document how they fit together. Data is structured for reuse whenever rights and context allow it. Interfaces remain inspectable, replaceable and interoperable, so each delivery strengthens a shared ecosystem instead of creating another closed dependency for its users.
Sovereign by design
We favour European hosting and architectures that can move between providers. Contracts, deployment procedures and operating knowledge stay with the organisation, not with a proprietary platform. Components can be replaced without rebuilding everything, and teams retain the access and documentation required to operate, audit and evolve their services independently.
Frugal by design
We treat resource use as an engineering metric, measured from development through operation. Software is profiled and adjusted before additional capacity is added. We select models and automation proportionate to the task, and use AI only where it delivers a clear benefit. Consumption becomes a design decision that teams can review over time. We also consider environmental impact and system longevity, favouring choices that reduce avoidable resource use and keep software maintainable over time.
ONE SENIOR TEAM, FROM FRAMING TO OPERATIONS
A senior team stays with each assignment from framing through delivery and operations. The same people shape the architecture, build it, document it and maintain it. Work is not passed through layers of subcontractors, so decisions retain their context and accountability remains clear.
Sustained work depends on a team that can last. We protect time for focus, honest discussion, recovery and individual needs. This is not an HR promise: care for the people doing the work preserves judgement, continuity and quality throughout the life of a system.
Client loyalty is earned through continuity, not asserted in a charter. Incorporated in August 2017, Foxcub still counts in 2026 among its clients an organisation first served under its name in December 2016. These are successive assignments, not one uninterrupted contract. Trust is tested in every delivery.