Brainy Devs
Language: English

One quarter
to launch.
One quarter
of support.

Brainy Devs designs, builds and launches AI-first products for companies: language-model assistants and generative features, shipped inside Android and iOS apps, web apps that take payments, and games. One fixed team, a scope fixed before the build starts, live in under three months, then three months of support. Projects from EUR 50,000 to 300,000.

Email clientes@brainydevs.com See how a project runs

Our own apps have passed 37 million downloads on Google Play, with a 4.4-star average from 418,000+ ratings, checked 12 September 2026. See what we’ve shipped.

Discovery, then one-week iterations with a build you can use at the end of each. Launch inside the third month; the empty week is the “under”. Then three months of support.

What can you build for us?

AI products, and the three kinds of product we build them into.

AI products and features, in production

LLM and generative-AI features in production for paying users: self-hosted vLLM, ComfyUI video pipelines on rented GPU fleets, token streaming over WebSocket and SSE, server-side credit wallets, and GPU cost control so the feature doesn’t eat the margin. Running today in Shimeji’s AI character generator and Yumeji’s animated wallpapers, and in Archibald’s mentor, which launches this month. If your product needs a model, we have shipped one. If it doesn’t, we will say so.

Android and iOS apps

Native Kotlin and Jetpack Compose on Android, Swift and SwiftUI on iOS, or cross-platform when it fits the product. We build the parts that turn an app into a business: in-app purchases on both stores, push notifications, offline-first data, and the store operations that start the day you go live.

Shipped: Shimeji and Yumeji on Google Play. Launching now: Archibald. All of our own apps are on Android, so the public proof on this page is Android; iOS work is native Swift and SwiftUI, on the same terms.

Web apps with Stripe

Node.js, TypeScript and React on Postgres or SQLite, packaged in Docker and run on DigitalOcean and Cloudflare. Stripe for payments, subscriptions and invoicing, so the product can take money from the day it launches.

Shipped on the web: the three properties behind Shimeji (a character catalogue, a community library and an AI generator). Our production billing today is Google Play Billing for subscriptions and one-time unlocks, plus server-side credit wallets; Stripe is the web equivalent and part of the stack we build with.

Games

Unity and C#, Android first. Sensor input, local multiplayer, Google Play Billing, and Firebase analytics and Remote Config so you can tune the game after release without shipping a new version.

Shipped: ShotMetric, a sensor-driven 3D sport-shooting range simulator, on Google Play.

What will it cost, and what’s the catch?

Between EUR 50,000 and EUR 300,000, for a scope we fix together before the build starts. The catch is that we work one way only, and we turn down the rest.

The terms

Budget
EUR 50,000
to 300,000
per project, for a scope fixed in discovery
Time to launch
Under 3 months
from the start of discovery to the product being live
After launch
3 months
of support, included, by the team that built it
Scope
Fixed in discovery, before the build starts. After every weekly build you re-plan the order and the detail with us; the scope itself changes only by agreement.
Team
Fixed for the whole project: senior engineers with an enterprise-consulting background. The team you start with is the team that builds it, launches it and supports it.
Delivery
End to end: discovery, design, build, launch, and the three months after. One partner accountable for the app, the backend, the payments, the store listing and the servers.

What we don’t do

Sell days. No day-rate consulting, no staff augmentation, no developers seconded into your team. Our senior engineers come from enterprise consulting; we sell products, not days.

Take work outside the range. If your project is under EUR 50,000, over EUR 300,000, or needs more than three months, we will say so at the first meeting.

Stop at the code. The store listing or the domain, the payments, the servers and the first three months are part of every project, because a product that isn’t live isn’t finished.

How will we know it’s on time?

Because you’ll be using it every week. Each iteration ends in a build you can open and show your own stakeholders, and you re-plan the next week with us from what you saw.

  • First meeting, then discovery. From then on, a build you can use at the end of every week.
  • Launch, inside month three. The empty cell is the “under”.
  • Three months of support, included.
The engagement model: discovery, weekly builds, launch inside the third month, then three months of support.
First meeting
Requirements and goals. What the product must do, what it must not do, who it’s for and what “launched” means for you. It’s also where we say so if the project doesn’t fit the range.
Discovery
The first part of the three months. It turns the first meeting into a fixed scope and a fixed team, and the clock on “under three months” starts here.
Every week
One-week iterations. Every week ends in a build you can use. Not a slide deck, not a demo on our machine: a build in your hands. Then you re-plan the next week with us: what stays, what moves earlier, what gets cut. The scope itself changes only by agreement; the order and the detail follow what you learn.
Launch
Inside month three. Store listings, payments, hosting and the release itself are ours to run, not just the code.
After launch
Three months of support, included. The same team stays on for the first three months of operation: fixes, store operations and support while real users arrive.

What we need from you: a first meeting about requirements and goals, then someone on your side who can try the build each week and take part in re-planning it.

Have you actually shipped anything?

Yes. It says very smart developers on the door, so here is the evidence: our own apps, three on Google Play and one launching, checked 12 September 2026.

Digital Cosmos is our in-house product studio, publishing on Google Play under that name. Many studios stop at the code. We keep our own products in production for paying users, so the parts of a launch that usually go wrong (GPU fleets, language models, billing, store operations and hosting) are already built, measured and rehearsed by the same team.

The team’s background is enterprise work: almost three years under contract with SGS, including a farm-improvement verification platform used on shrimp farms in Vietnam for a US aquarium’s sustainability programme, and two years building an industrial web HMI at Measuresoft in Ireland.

Across our own apps: 37 million downloads on Google Play (Shimeji alone sits in the store’s 10,000,000+ bracket), 418,000+ ratings with a 4.4-star average, 4 products live or launching, shipped in 24 languages, and GPU fleets and LLMs running in production for paying users.

Download brackets and rating figures are from Google Play, checked 12 September 2026, and link to the listing they come from. The 37 million total is from our Play Console on the same date.

Shimeji: Screen Buddies

What it is
Animated original mascots that walk across your Android screen on top of other apps. 22+ original characters, an in-app character editor, and AI character generation on a GPU fleet: describe a character, get it animated.
What we built
Kotlin and Java app with an overlay engine tuned for battery and smoothness; Node.js services; Docker GPU workers on vast.ai; three web properties (a catalogue, a community library and an AI generator); rewarded ads, a subscription and one-time unlocks; 24+ languages.
On Google Play
10,000,000+ downloads on the listing; 37 million installs in our Play Console
4.4 stars from 418,000+ ratings

What else do people ask?

Do you build for iOS as well as Android?

Yes. Native Swift and SwiftUI on iOS, native Kotlin and Jetpack Compose on Android, or cross-platform when it fits the product. Our own products are published on Google Play, which is why the public proof on this page is Android.

Can we hire one or two of your developers by the day?

No. We don’t sell day rates or staff augmentation. We build a fixed-scope product with a fixed team, launch it and support it for three months.

Our project is bigger than EUR 300,000 and will run for a year. Will you take it?

No. We take small and medium projects, between EUR 50,000 and EUR 300,000, that can launch in under three months. If yours is bigger we’ll say so at the first meeting rather than take it and stretch.

Do you work with startups?

Yes. Founders of funded companies are among the people we build for, when the project fits the range.

What does “under three months” count from?

From the start of discovery, the first week of work after the first meeting, to the product being live.

What if we want to change something halfway through?

You will, and the weekly re-plan is for exactly that. After each build you decide with us what the next week is for. The scope itself changes only by agreement; the order and the detail move with what you learn.

What do you need from us?

A first meeting about requirements and goals, then someone on your side who can try the build each week and take part in re-planning it.

Who owns the code, the store listing and the servers?

You do. We build in accounts you own from the start: the repository, the Google Play or App Store developer account, the domain and the hosting, on DigitalOcean behind Cloudflare. There is nothing to hand over, at launch or when support ends.

Is the AI real or a demo?

Real. Shimeji generates animated characters on a GPU fleet for paying users; Yumeji animates photos with a video model on the same kind of fleet; Archibald, launching now, runs on self-hosted vLLM and streams tokens to a phone. We have paid enough GPU bills to know how to keep them down. When a product doesn’t need a model, we leave it out.

What happens after the three months of support?

Support ends and the product stays yours. The stack is standard: Docker, Postgres or SQLite, Node.js, DigitalOcean, Cloudflare, so it can be run by any competent team. If you would rather we kept running it, that is a separate agreement.

What do you build with?

Kotlin and Jetpack Compose, Swift and SwiftUI, Unity and C#, TypeScript, React, Node.js and Express, SQLite and Postgres, Docker, vLLM, ComfyUI, WebSocket and SSE, Stripe, Google Play Billing, Firebase, DigitalOcean, Cloudflare, vast.ai GPUs, nginx and Let’s Encrypt. The team also has a background in Angular, .NET and Java. Most of this is what our own products run on in production; the rest is what we reach for when a client’s product needs it.

What happens when we write to you?

You get a reply from the team that would build it, and a first meeting about requirements and goals.

Email clientes@brainydevs.com with what you want to build, who it’s for and when you need it live. A paragraph is enough.

There is no form on this page. A brief written in your own words tells us more than a form would, and it lands in a mailbox we read.

Brainy Devs, Cambrils, Tarragona, Spain. We work remotely across Europe and come on site in Barcelona and Tarragona when it’s useful.

Email clientes@brainydevs.com