Services
Five things we do, and the evidence for each one on this site.
Service pages are usually a list of capabilities nobody can check. These five are arranged so that you can: each one names the case that backs it, and each case names what was measured, what was not, and what we are not allowed to say.
If you already know which one you need, the cards below go straight there. If you do not, the quickest route is the section after them — it starts from what you already have rather than from what we sell.
-
End to end
Custom software
Discovery, architecture, build, launch and handover. A fixed price for each phase rather than a number invented for the whole system before anyone knows what it is, a small first release that real people actually use, and a handover designed so that somebody else could maintain the result.
- Evidence
- Smart Comune · Paytec OPTO
- Java
- Spring Boot
- Jmix
- .NET
- C#
- Flutter
- Dart
- Node.js
- TypeScript
- Django
- PHP
- Laravel
- Vue
- React
- Next.js
- Three.js
- Tailwind
- PostgreSQL
-
Capacity
Dedicated teams
Named engineers inside your repository, your sprint and your standards, on your priorities, for a fixed period with an end date in it. A contract for services rather than staff leasing — a distinction Italian law draws substantively, and one we explain rather than bury.
- Evidence
- The arrangement is described in full, including the statute
- Java
- Jmix
- .NET
- Python
- Flutter
- DevOps
- Kubernetes
- Ansible
- GitLab CI
- iOS
- Android
-
Replacement
Legacy modernization
Systems that still run the business and that nobody wants to touch — usually because a vendor ended support, a store changed its rules, or the people who understood it have gone. Assessed first, then migrated in waves with the old system running alongside until the new one has earned the traffic.
- Evidence
- Paytec OPTO · CUBA Platform migrations
- Xamarin → .NET MAUI
- CUBA → Jmix
- Legacy Flutter
- Kubernetes migration
- .NET 8/9 → .NET 10
-
Models and evidence
AI & data
Classification, detection and decision support where the answer has to be defensible — a compliance officer, a regulator or an analyst has to see why the model said what it said. Trained on your data, measured against your baseline, and reported with the failure modes named.
- Evidence
- SMS threat detection · regulatory compliance monitoring
- PyTorch
- Bayesian inference
- Text classification
- sCASP
- LLM
-
Telecommunications · wholesale
Messaging
A2P SMS termination sold wholesale to operators and aggregators, into nine destinations across the Caucasus, Central Asia, the Gulf and the EU. Far Rainbow contracts as principal rather than as an agent, holds the general authorisation for enterprise messaging, and will tell you which routes are direct.
- Evidence
- ROC 44178 · general authorisation, MIMIT
- A2P
- OTP
- SS7
- SMPP
- Interworking
Start here instead
What you already have decides what you need
Most people arrive knowing the problem and not the category. These five sentences route faster than a capability list does.
You have the plan and the people who understand the domain. You are missing hands.
Capacity inside your own process, on your priorities, for a defined period. You keep the technical direction; we keep the employment relationship.
Dedicated teamsYou have the problem. The system that solves it does not exist yet.
Discovery first, then a small first release in production, then waves. Each phase priced before it starts, and a handover rehearsed at the end of each one.
Custom softwareYou have the system. It works, and it is becoming impossible to keep.
An assessment before a plan: what moves untouched, what is converted, and what has to be written again. Usually a smaller list than anyone fears.
Legacy modernizationYou have the data. What you need is a decision somebody can defend.
Classification and detection where a regulator, a compliance officer or an analyst has to see the reasoning, not just the score.
AI & dataYou buy SMS termination, and nobody will tell you how many hops are in the route.
Wholesale A2P into nine named destinations, from an Italian counterparty contracting as principal, with direct and partner routes distinguished before the contract.
MessagingNone of these is quite it.
Describe the problem in two paragraphs and we will tell you which of the five it is, or that it is none of them and who would be better placed.
Write to usTrue of all five
The commitments that do not change with the service
These are the same whether we are building a system, lending you engineers or delivering your traffic. They are written here once rather than repeated as adjectives on five pages.
- Named people, not profiles. You meet the engineers before the contract, and we tell you each person's weak spot rather than letting you find it in week three.
- Your repository from the first commit. Not at the final invoice, and not as an import of a finished codebase with the history flattened.
- Fixed price per phase. For a phase whose scope is known. A fixed price for a system whose requirements are still being discovered is a bet, and somebody loses it.
- A handover somebody else could use. A build that runs on a clean machine, migrations from empty, a runbook, decision records — and a stranger who can make one change and release it.
- Figures we can defend. If a number is not measurable, it does not go on this site. That rule is why some of our pages are shorter than a competitor's.
A special case
Where Jmix sits in all this
Jmix is a Java platform we work in constantly, and Far Rainbow is the seller of record for its licences in Italy. That makes it a platform, not a sixth service — three of the five above have a Jmix-specific version with the detail a Java buyer actually wants. If the platform is already decided, start there.
If the platform is not decided yet
An architecture review answers whether Jmix suits the system you are describing, and the answer is sometimes no — the five situations where we say no
If you are leaving CUBA Platform
The framework reached end of life, including security updates. Most of a CUBA system moves untouched — what moves, what gets rewritten, what has no replacement
If you need Jmix engineers specifically
They are scarce in Italy, and the honest version of that page says how many and how fast — how many, how fast, and who directs what
If you want the whole system built on it
What you own at the end, what the premium add-ons commit you to, and the test that says the handover is finished — built end to end, and handed over
What we actually work in
The stack, as evidenced by delivered work rather than by a logo wall
Everything below has carried something into production for a paying client. Some of those engagements are published as cases on this site and some are covered by agreements that stop us naming the client — but nothing here was learned for a demonstration or used once, which is the whole reason a list like this is worth reading.
Java and the enterprise side
Java, Kotlin, Spring Boot, Jmix and CUBA Platform, PostgreSQL. Internal systems with a large domain model, a real access model and a maintenance horizon measured in decades rather than quarters.
.NET and native mobile
C#, .NET 10, .NET 6, ABP Framework, .NET MAUI, iOS and Android — including taking over a payment application still running on Xamarin a year after Microsoft stopped supporting it, and moving it without an outage.
Cross-platform mobile
Flutter and Dart, including a product whose four applications — customer, seller, venue and administrator — share one codebase against a single Node.js and TypeScript backend with TypeORM, PostgreSQL, Firebase and Stripe.
Web and front end
React, Next.js, Vue, TypeScript, Tailwind, Three.js for interactive 3D, and on the server side PHP with Laravel, Django, Node.js with Express, SCSS. The unfashionable half of this list is the half carrying payment traffic today.
Infrastructure and delivery
GitLab CI/CD and automated test pipelines, Ansible, Docker, Kubernetes — including migrating legacy applications into it — Linux on Ubuntu and Debian, monitoring, and the certificate management nobody puts on a slide.
Models and data
PyTorch, GPU training, Bayesian change-point detection, text classification that survives deliberate obfuscation, and sCASP with Event Calculus where the reasoning has to be shown rather than trusted.
Design and specification
Figma for interface design, OpenAPI for contracts between the parts, and the business-process modelling that comes before either — we have been hired for the design stage alone, with somebody else building the result.
Next step
Describe the problem, not the solution you had in mind
Two paragraphs are enough. If one of the five fits, we will say which. If none does, we will say that too — it happens often enough that it is worth promising.