A ready AI agent team for your tech stack: the ten teams in ULU
· 10 min read · by EndorphinLab, the makers of ULU
You do not need to know what a "tech stack" is to get an AI agent team for your app. ULU comes with ten ready teams, one for each popular stack, and this guide explains in plain words what each one is for and how to pick.
- ULU ships ten ready-made AI agent teams: Node/React, Next.js, FastAPI/React, Go/React, Django, Rails 8, Laravel, Elixir/Phoenix, Flutter/Firebase and Expo/Supabase.
- A ready team already has its roles set for the stack, and ULU runs the stack's own tests and shows the counts as a pyramid.
- If none of the ten fits, Kukulu, the builder bee, designs a custom team from your description.
- To choose, think about what you want to build, where it will run and whether a developer friend knows one of the stacks.
- Your first project in ULU is free, so you can try a team before you pay for anything.
Why a stack matters, and why you can ignore most of it
A "stack" is the set of tools a developer uses to build an app: the programming language, the framework around it, the database and the way the app is tested.
If you have no technical background, the choice can feel like picking an engine for a car you have never driven. You rarely need to understand the engine. You need to know roughly what you are building. This guide helps you match that to one of the ten teams in ULU.
ULU is a desktop app for Claude Code, Anthropic's agentic coding tool. You describe your project in plain words, and ULU manages a team of AI agents, called bees, that plan, design, build, test, secure and ship it. If you want the big picture first, read what an AI software factory is or AI agent teams explained.
What kind of app is each stack usually chosen for?
Almost every app is a web app, an API with a web front, a mobile app or a real-time app. Here is how the ten stacks usually line up. These are general descriptions, not rankings. Any of them can build more than the group it is listed under.
Node/React
Node lets a developer write the server side in JavaScript, and React is a popular way to build the screens people click on. Together they are often chosen for a web app where one language runs everywhere. The ULU team for this stack uses Express, Prisma, React with Vite and PostgreSQL.
Next.js
Next.js is a framework built on React for web sites and web apps. It puts the screens and the server logic in one project, which many people like for products that need to show pages to visitors and also act as an app. The ULU team uses the App Router, server actions, Prisma and PostgreSQL.
FastAPI/React
FastAPI is a Python framework for building an API, which is the part of an app that other programs talk to. React supplies the web front. This pairing is often chosen for an "API plus web front" product, especially when you may want other tools or a mobile app to use the same API later. The ULU team adds SQLAlchemy, arq jobs and PostgreSQL.
Go/React
Go is a programming language often used for servers and APIs. With React for the screens, this is another "API plus web front" choice. The ULU team uses chi, sqlc, River jobs, React and PostgreSQL.
Django
Django is a web framework in Python that comes with many common parts already included, such as user accounts and an admin area. It is often chosen for web apps that manage data: members, orders, content. The ULU team uses HTMX, Celery and PostgreSQL.
Rails 8
Rails is a web framework in Ruby known for building web apps quickly. It is a common pick for products where you want to get a working web app in front of people early. The ULU team uses Rails 8 with Hotwire, Solid Queue and PostgreSQL.
Laravel
Laravel is a web framework in PHP. PHP has been used for web sites for a long time, so Laravel is often chosen for web apps and for projects that will be handed to developers who already know PHP. The ULU team uses Livewire, queues and PostgreSQL.
Elixir/Phoenix
Phoenix is a web framework in the Elixir language. It is often chosen for real-time apps, where the screen updates live as things happen: chat, dashboards, live boards. The ULU team uses LiveView, PostgreSQL and Oban. It is the team the other nine are made from.
Flutter/Firebase
Flutter is a toolkit for building iPhone and Android apps from one shared codebase. Firebase is a set of ready-made back-end services from Google. This is a mobile app choice. The ULU team uses Firestore, Auth and Cloud Functions.
Expo/Supabase
Expo is a toolkit for building mobile apps with React, and Supabase is a back-end service that provides a database and sign-in. This is also a mobile app choice. The apps it produces are ones you can see live in the Phone tab inside ULU.
The ten stacks side by side
| Stack | Usually used for | Team's testing tools |
|---|---|---|
| Node/React | Web app | The stack's own test tools |
| Next.js | Web app and web site | The stack's own test tools |
| FastAPI/React | API plus web front | The stack's own test tools |
| Go/React | API plus web front | The stack's own test tools |
| Django | Web app that manages data | The stack's own test tools |
| Rails 8 | Web app, built quickly | The stack's own test tools |
| Laravel | Web app | The stack's own test tools |
| Elixir/Phoenix | Real-time app | The stack's own test tools |
| Flutter/Firebase | iPhone and Android app | The stack's own test tools |
| Expo/Supabase | iPhone and Android app | The stack's own test tools |
Why does the last column repeat itself? Because each team uses the tests that belong to its stack. ULU runs your project's own test suites, in tools like Jest, Pytest or Playwright, rather than inventing a separate checker.
What "a ready team" means in ULU
A ready team is a team of AI agents that is already set up for one stack. You do not start from an empty page and wonder who should do what. The roles are there from the first click.
Every ready team follows the same flow. It plans, designs, builds, reviews, tests, secures and deploys, and it stops for your approval on the design and on the release. Only the stack changes. The roles include a Product Manager, a Tech Lead or Architect, a Designer, a Developer, QA, Security and Release, and they work one after another. You can watch the hand-offs in the hive view, where each agent is a bee in its own cell and El Capitan, the orchestrator bee, passes work from bee to bee.
Roles set for the stack
The Developer bee on a Rails 8 team works in Rails. The one on a Flutter team works in Flutter. You see the team as a honeycomb, change what you like and approve it.
Tests that match the stack
ULU runs the project's own test suites at three levels: unit tests check small pieces, integration tests check that pieces work together, and end-to-end tests walk through the app like a user. It shows the counts as a pyramid, so you can see at a glance how much is covered. If a build check finds a leftover placeholder or a missing file, ULU asks Claude to repair it.
What happens when none of the ten fits
Maybe your idea is a mix, such as a web app and a phone app, or it needs something not on the list. In that case Kukulu designs a custom team from your description.
The path is the same four steps as for a ready team. You define your project in your own words, ULU generates the agents, you build the team, and the team lives in your project folder inside Claude Code. Kukulu writes a project brief, asks only about what is missing, and three reviewers add the questions you did not think of.
Which is better for you, a ready team or a custom one, depends on the project.
How to choose: three questions
1. What do you want to build?
- A web app that people use in a browser: Node/React, Next.js, Django, Rails 8 or Laravel.
- A product with an API behind it and a web front: FastAPI/React or Go/React.
- A real-time app where the screen updates live: Elixir/Phoenix.
- An app for iPhone and Android: Flutter/Firebase or Expo/Supabase.
If you are unsure, describe the idea to Kukulu and see which team it suggests. You approve the design before anything is built.
2. Where will it run?
A web app runs on a server and people open it in a browser. A mobile app is installed on phones. Decide which of those is closer to what you picture. If people will mostly use it on their phones as an installed app, look at Flutter/Firebase or Expo/Supabase. If they will use it on a laptop or in any browser, look at the web stacks.
3. Do you have a developer friend?
This one is practical. If a friend or a future hire knows Python, Ruby, PHP or JavaScript, pick the team for that language. Someone can then read, fix or extend the code later. If you have no one, any of the ten works, because the bees do the building and the team stays in your project folder.
What it costs to try
Your first project in ULU is free, and every project after that takes a paid place on a license key. You also need your own Claude plan or API key, because the agents run in Claude Code and use it. Every step shows its running cost in USD, its time and its file log, so you see what a team spends while it works. For the longer story, read what AI agents cost. If you have never opened a terminal, Claude Code without coding shows how ULU puts a window on top of Claude Code. You can follow the spend live in the tracking view.
Questions people ask
Can I switch stacks after I start?
A stack is chosen when the team is built, so changing it later means building a new team for the new stack. For that reason it is worth spending a few minutes on the choice. Whether an existing project can move over depends on the project.
Do I need to know the programming language?
No. You describe the project in plain words and the agents write the code. It does help to have someone who knows the language later, which is why the developer friend question is on the list.
How do I know the team's work is any good?
ULU runs the project's own tests and shows the counts in the test pyramid, and the team stops for your approval on the design and the release. It does not promise a quality level. It shows you the evidence so you can judge.
Try it
Pick the kind of app you want, describe it, and let Kukulu show you the team. Install ULU and start your first project for free. If you want to see it first, the video walks through a build.
