Multi-user testing for solo builders

Your app needs people.
You’re building alone.

Test chats, communities and collaborative apps without rounding up a group. AI participants use separate accounts in your app. You join in, check both sides and keep building.

Set up test participants See the workflow

Your API key or workspace-managed AI. A free playground to start.

Your app

A group chat, with a group.

Plan a weekend away. Alex has a budget. Maya changes the plan.

MayaThe organiser

AlexThe careful planner

SamThe late arrival

MayaCould we leave Friday instead? I found a place by the coast.

AlexFriday works. Can we keep it under £150 each?

SamI’m checking trains. Add me to the weekend group?

Illustrative scenario3 distinct perspectives

Build the interactions
that need other people.

Messaging & communitiesInvitations & shared activityTeams & collaboration

From testing alone
to testing together.

Set up separate test accounts, give each participant a goal and join the interaction in the app you’re building.

Give Jango a place to go

Add your development URL and test accounts. Each participant gets their own isolated browser.

Choose who shows up

Set their roles, relationships and goals. Tell one person to change the plan. Let the others respond.

Join in and check both sides

Use your app alongside the participants. Inspect their screens, pause when something breaks and save the cast for your next change.

Every run leaves
something useful behind.

A repeatable situation. A navigation hint backed by an actual action. Evidence that an expected message appeared. Jango keeps the context you’d otherwise rebuild tomorrow.

Explore app memory

App knowledge

Known identities

Roles, relationships and encrypted login state

Observed app controls

Reusable hints with execution history

Run evidence

Activity, observable checks and comparisons

Fits where you build.

Use the dashboard, launch from your terminal, or give your coding assistant access through MCP. The cast and its memory stay together.

CLIMCPWorkspace APIPortable casts

Terminal

# Connect from Developer tools, then bring in your cast
node ./jango-cli.mjs start <cast-id> \
  --live --ai byok

# Change the situation
node ./jango-cli.mjs direct <session-id> \
  "Maya, invite Alex to the group"

Start small.
Build something social.

Local preview is available now. Hosted plans below are proposed launch pricing; subscriptions are not being sold yet.

Playground

Free

Explore casts and scenarios with scripted participants. No AI key required.

Try the playground

Builder · proposed

$49/month

A proposed hosted plan for individual builders. BYOK model usage would be billed by your provider.

Explore the local edition

Studio · proposed

$149/month

A proposed hosted plan for teams and larger casts. Capacity and managed AI allowances are being evaluated.

Explore the workspace

Local BYOK has no Jango subscription today; provider charges apply.Managed AI requires operator configuration.

Test the parts that need other people.

Social app testingTest social app interactions with AI participants: invitations, conversations, community roles and shared activity, alongside your own test account.Chat app testingTest messaging and group chat flows without asking friends to log in. Direct AI participants in separate browsers and join the conversation yourself.Collaboration testingUse AI participants to explore team invitations, shared tasks and role-based workflows in collaborative web apps, without gathering a testing team.The solo developer’s testing guideA practical workflow for testing social and collaborative apps alone: separate accounts, purposeful scenarios, AI participants and checks across browsers.

A few things to know.

Are these real people?

No. They’re AI participants acting through real browser sessions. They help you exercise interactions and explore scenarios; they don’t replace research with real users.

Can I join the cast in my own app?

Yes. Log into your app as yourself while the cast uses its assigned accounts. Use Jango to give directions, pause participants or inspect their screens.

What is supported today?

The local edition supports live browser actions, OpenAI, Anthropic and Vercel AI Gateway connections, operator-managed AI, saved casts and memory, CLI and MCP. Use development accounts. Canvas-only apps, popup sign-in flows and CAPTCHA may need a different integration.

Where does my data go?

Workspace data and encrypted credentials are stored on your Jango server. Relevant page text, goals and participant memories are sent to your selected AI provider. Browser destinations are restricted to your configured app origins.

Stop being every user.

Bring in your cast

Your app needs people.You’re building alone.