We run what we build.
GPbot and Herald are products we use in real operating conditions. That changes the standard: edge cases, bad inputs and handovers are product work, not someone else’s problem after delivery.
Independent design & engineering studio
Built to impress.
Engineered to work.
Codolie
01 / Our commitment
We build and operate the systems behind ambitious digital businesses.
Based in Mallorca. Working globally.
From product architecture and AI agents to data, infrastructure, and automation, we take responsibility for the entire technical foundation.
We work close to the business, own the hard technical decisions, and remain accountable long after launch.
02 / Selected work
Selected work.
Products, platforms and operating tools built for specific businesses and the people who rely on them.
Our product
GPbot - AI Content Engine
We built this for our own media properties — 24 articles in Google Discover in week one. It's now the engine behind FinalBoss-Engine deployments.
01AIContent MarketingSEOSee Details ↗
Client work
Base.Tube
YouTube, but you actually own your content. Decentralized video platform on Base chain with IPFS storage. Creators keep 100% of their audience.
02Web3Video StreamingIPFSSee Details ↗
Client work
Omnibutler - AI Financial Admin
Invoice processing that passes audits. Deterministic validation on every extraction — documents that don't pass don't get routed. Microservices architecture built for volume.
03AI AgentsMicroservicesExpress.jsSee Details ↗
Our product
Herald - AI Social Media Agent
One prompt, five platforms. Built for our own publishing: AI writes platform-native content for X, TikTok, Reddit, Facebook, and LinkedIn, then generates the video.
04AI AgentsMulti-LLMSocial MediaSee Details ↗
03 / Why Codolie
We build products. We run them, too.
A digital business is more than its launch. It is the systems that carry orders, content, decisions and customer relationships when nobody is watching. We build those systems, then stay close enough to improve them.
The engineering stays in the room.
You work with the people making the technical calls. Questions do not travel through layers of account management before they reach the architecture, code or infrastructure.
We build around the business you actually have.
We connect the tools, data and workflows already doing useful work, then replace the parts that create friction. The goal is a durable operating system, not a showcase prototype.
04 / Our expertise
The technical foundation, from interface to operations.
A clear website or app is only the visible layer. We take care of the product decisions and the machinery behind it, so the experience has somewhere reliable to stand.
Websites and product engineering
Websites, customer portals and applications designed around a real decision, transaction or piece of work.
- Product architecture
- Interfaces and design systems
- Customer and operator tools
05 / How we work
How we work.
We make the next decision visible, build enough to test it in context, and keep the work connected to the business it is meant to support.
We look at the current operation, the people involved, the systems in play and the constraint that is actually holding progress back.
We decide what deserves to be solved now, what must be true for it to work, and what can wait until there is evidence to justify it.
We shape the core journeys, technical architecture and operating rules together, including ownership, permissions and the places where things can fail.
We deliver working increments against the actual data and services wherever possible, so review is about the product in use rather than a promise of it.
We prepare the release, watch what the system reveals, and agree the next piece of work deliberately. Ongoing involvement is planned around the product’s needs, never assumed without a scope.
06 / What we believe
Engineering is taking responsibility for what happens next.
Every technical choice has consequences: what a team can change, what a customer can trust, what it costs to run the product. We want to understand those consequences before committing to an architecture, a framework or an AI model.
Building our own products gives us a place to test new approaches and live with the results. We carry that experience into client work: clear interfaces, explicit rules, recoverable failures and systems the next engineer can understand.
07 / Insights
From the studio.
What we learn while shipping products, connecting infrastructure and putting AI into real workflows.
Client Success
What Our Clients Say
01 / 04
01
“Communication is straightforward, and they understood our needs like few have. They rebuilt our trading algorithm from scratch, and the support after has been truly exceptional. They're now our go-to whenever we need technical work.”
02
“It was really hard to choose the right team to build our DeFi app. But Codolie exceeded my expectations. Their knowledge in web3 is unmatched—their advice helped us avoid big mistakes in the architecture we originally planned. Simply the best.”
03
“I wanted a simple website. I got a Rolls Royce.”
04
“I wanted a beautiful Shopify store, but nobody offered me the custom solution Codolie suggested. At first I didn't believe it would work—I'm so thankful I trusted them. My store is fast and absolutely beautiful!”
Codolie
What are you building?
A product that needs to become operational, a website that needs a stronger job, or a system that has outgrown its tools. Start with the situation and we will define a useful next move.