Teams

Build together, on one plan

Make a team for your company, your agency or your class. Everyone builds in one place: the team’s apps, credits, brand, domains and servers are shared, and its Admins decide who does what.

Teams are here. Team plans for up to 5, 15, 30 or 50 people, each with everything in Pro for the whole team.

How a team builds

From an idea to a published app, with the right people at each step

1

Make a team

Choose a Team plan and name your team; you’re its first Admin.

2

Invite people

Invite them by email as Viewers, Testers, Builders or Admins.

3

Build together

Builders and Admins make and change apps on the team’s credits; Testers try them and leave feedback.

4

Publish

Put apps online on the team’s servers and domains, and every version is kept.

Who does what

You decide each person’s role

Four roles, from seeing the team’s apps to running the team. An Admin changes anyone’s role at any time.

SeeTry and give feedbackBuild, change and publishDelete appsMembers and the plan
Admin✓✓✓✓✓
Builder✓✓✓––
Tester✓✓–––
Viewer✓––––

One organisation

Everything your team needs in one place

Single sign-on with SAML (coming soon)

Your people sign in with your company’s identity provider.

Members in one place

Invite people by email, change their roles and remove them when they leave.

One plan and one balance of credits

One Team plan and one balance of credits the whole team shares, topped up by its Admins.

Usage by person and app

Admins see each month’s credits by person and by app, and can download them. Everyone else sees their own.

Shared apps and versions

Your team’s apps, plans and versions together, with every version kept.

Your GitHub

Code in your organisation’s own repositories, every change as a pull request.

The team’s own brand, business details, domains and servers

Its Admins set them up; domains and servers are paid from the team’s credits.

Questions

About teams

How does billing work for a team?

One Team plan and one balance of credits for the whole team, bought and topped up by its Admins, who see each month’s usage by person and by app.

Who can build?

Builders and Admins make, change and publish the team’s apps; Testers try them and Viewers see them.

What happens when someone leaves?

An Admin removes them on Members. The team’s apps, versions and credits stay with the team.

Can we keep the code in our company’s GitHub?

Yes. Connect your organisation’s GitHub and every change arrives as a pull request in your own repositories.

Do we need single sign-on to start?

No. Make a team today; company sign-in with SAML or OIDC is coming soon. For organisations, see Enterprise pricing.

Bring your team

Make your team today and invite your colleagues.