Prospecting, production, market watch, follow-ups: the firm is run by the system it designs for its clients — agents under human approval, journaled decisions. It's our permanent test bench, and the first thing we show you in a meeting.
OpenUp Agency is a digital engineering firm based in Papeete, part of the RLF Group. Four trades under one roof — web development, Odoo ERP, automation, AI agents — to run projects most agencies subcontract in cascade. We work for companies and institutions across French Polynesia, the French-speaking Pacific and the Asia-Pacific region.
Sites, business apps, portals — the front end of the systems.
Configuration, integration, self-hosting — the management backbone.
The flows between your tools, executed and monitored.
The layer that reads, proposes, acts — under approval.
We open one project per month. No more.
That's what protects the standard — and why the audit is the way in.
Company director, former management controller, architect who still writes code. Three vantage points that set the firm's standard.
Founder · Company director
I run several companies in French Polynesia. A company director first: I know what a system has to hold up every day — cash, stock, teams, deadlines. OpenUp designs with that eye.
Before founding companies: management control, in-house and in consulting, up to budget advisory for institutions of French Polynesia. Years on the side of the table that arbitrates budgets and reads commitment files. That's the language our projects speak: scope, documents, firm costing.
Today I design the architectures and I still write code. OpenUp was born from a simple conviction: in French Polynesia as anywhere else, agentic AI deserves the standard of an IT project — not that of a subscription app.
The sales pipeline, follow-ups, content production, market watch and project tracking run on our own agent system: each agent reads, proposes, prepares — and a human decides. Committing actions go through approval, decisions are journaled, usage cost is tracked per case. It's the same standard we deliver. In meetings we don't describe it — we open the cockpit.
The standard isn't declared, it's observed: signed systems in production, engineering artifacts, owned capacity.
Four principles, held in writing — on the project side, the team side, the client side.
Set in the written architecture, not along the way. If we overrun, that's our problem — not yours.
Code, documentation, exportable data. You leave with the complete system if the engagement ends — it's in the contract.
The firm runs on its own agents, under human approval. If it breaks, we're the first to know.
Based in Papeete. On site when the project calls for it — immersion in your real processes is part of the method.
We look at one of your processes, we show you what a system in production changes — and we tell you what it costs, in writing, before we start. If it's not at our level of intervention, we'll tell you that too.