Trust & references
Young firm. Transparent about it.
Enterprise buyers have every right to ask "who else have you done this for, and how did it go?" This page answers that question honestly — including what we can't show yet and how we make up for it.
Why no public case studies — yet.
Our clients operate in regulated sectors — finance, healthcare, government, legal. Most of them do not want their vendors publishing their names alongside "we automated their compliance workflow with AI" on a marketing site. Understandable. We honor that.
{brand} is also a deliberately young services firm. We started from zero. We haven't bought logos. We won't fabricate them. The ones we eventually publish will be the ones clients specifically authorize us to name.
Both facts — regulated-sector NDAs and being young — are real and won't change quickly. So instead of faking proof, we've structured the commercial relationship so that not having public case studies should not be a barrier to engaging us.
What we offer instead of logos.
Four concrete mechanisms that reduce your risk more than a client testimonial would.
Fixed-scope, fixed-price pilot
Every engagement starts with a 3-Month Pilot at 6.000 € (4.500 € for engineering deployments). Scope, deliverables, and KPIs are written before any work starts. If we scope it wrong, that's on us.
Walk-away built in
Everything we deploy is open-source, on your infrastructure. If you end the engagement, the system keeps running. We are incentivized to keep you happy, not to lock you in.
Technical references on request
Up to 2 current clients agree to take reference calls under NDA during Discovery. You speak to real engineers running live deployments. We facilitate the intro, not the script.
Weekly KPI reviews, visible failure
Pilots have weekly KPI reviews with your team. If something's broken, you see it in week 2 — not month 3. We commit to continuing only if the KPIs support it.
Typical shape of a first engagement.
These are structural patterns — not specific clients, not specific numbers. They describe the kind of scope a sector tends to engage us for, so you can gauge fit before a Discovery call.
A mid-market EU or GCC financial services firm with a compliance obligation that prevents using SaaS AI. Typical scope: deploy Private AI Assistant for the compliance/risk team, RAG on regulatory circulars, SSO via their IdP. 4–6 week deployment, Essential or Professional Operations tier after pilot.
A hospital network or clinical research group that cannot route patient documents through external AI. Typical scope: self-hosted LLM backend + Private AI Assistant with clinical guidelines indexed, role-based access tied to their identity provider, audit trail retained under their policies. 6–8 weeks.
A law firm or in-house legal team evaluating AI under professional secrecy obligations. Typical scope: Private AI Assistant with per-matter compartmentalization, multilingual (EN + client languages), contract and precedent corpus indexed. 3–5 weeks for pilot, then expansion per matter.
A mid-market company with 20–50 engineers using fragmented AI dev tools. Typical scope: AI-Native Development Platform deployed across workstations, private model backend, curated MCP extensions. 4–6 weeks to full rollout. Typically standardizes the whole engineering stack on one governed platform.
Structural patterns. Specific scope, pricing, and delivery for your context are scoped during Discovery.
Facts about us, for procurement.
The disclosures most procurement teams ask about before a first engagement. Items marked "Disclosed on signed SOW" or "Available on request" are standard commercial posture — not a dodge.
- Operating regions
- EU + UAE
Active deployment capability in EU data centers and UAE sovereign clouds (AWS ME, Azure UAE, G42 Cloud, OVHcloud EU).
- Engagement model
- Fixed-scope pilots + annual Operations
Pilot pricing is fixed in writing before work begins. Operations contracts are annual with a 30-day exit clause.
- Data handling
- Self-hosted by default, no third-party AI APIs
Client prompts, documents, and logs stay inside client infrastructure or our single-tenant managed hosting. No external AI vendors in the loop unless the client explicitly adds one.
- Data Processing Agreement
- GDPR Art. 28 DPA available on request
Signed before any processing of personal data. UAE PDPL annex available for GCC-hosted deployments.
- Legal entity
- TROPICALNET FZCO
Free Zone Company incorporated in Dubai under the International Free Zone Authority (IFZA). Registration number disclosed on signed SOW.
- Founded
- 2021
- Professional indemnity
- E&O coverage maintained for active engagements
- Technical references
- Up to 2 references available under NDA during Discovery
Clients agree to participate as references on a per-engagement basis. Client list is not published — by their preference, not as a hiding mechanism.
- Published case studies
- Scheduled for publication as clients approve
- Open-source contributions
- Disclosed under Discovery
- ISO 27001 / SOC 2
- Not currently certified — roadmap disclosed on Enterprise engagements
Want a technical reference before signing?
Start with an AI Assessment. During Discovery, we'll facilitate a reference call with a current client under NDA — no script, just their experience.