Team Plan
Team is the first adult-level collaborative plan. It is intended not so much for heavy computational builds, but for organizing real teamwork: multiple participants, a shared project space, roles, and a more stable process.
What is included, what limits apply, and when it is time to move to the next level
If Free is the entry point for one person, Team is already a managed environment for a group. It introduces a shared project rhythm rather than just the personal work of a single engineer.
What is included in Team
This plan is designed for small working groups that already need more than simply building firmware — they need to coordinate people, materials, and project actions.
- A shared project space, collaborative work on tasks, and a basic model of roles within the team.
- Up to 5 team members, a shared contour for projects, comments, internal actions, and coordination.
- Higher limits for standard builds and more comfortable teamwork compared to Free.
What limits apply to Team
This is already a full team plan, but not an industrial high-load layer and not a service package with heavy support.
- Up to 25 standard builds per month, up to 5 team members, and up to 10 active projects at the same time.
- Limited access to the priority queue and no heavy build contour of the kind available in Build+.
- No official SLA, no dedicated specialist, and no support layer at the Support level.
What is not included in Team
Team solves small-team organization, but it does not replace the heavy build package or the official service layer.
- No extended compute priority for deep and resource-intensive builds.
- No architectural consultations, official сопровождение, or fast service response from VOSCOM.
- No private corporate contour, certification, pilot launch, or on-prem scenarios.
How Team is better than Free
Team is needed when the project stops being purely personal and begins to require normal organizational discipline.
- Unlike Free, it introduces real collaboration on a shared set of projects and actions.
- Limits are higher: the team can do more builds, manage more projects, and work more steadily.
- A manager or lead gets a minimally adult management layer instead of just a set of separate accounts.
When Team fits best
This plan is suitable for those who have already gathered a small working group around an initiative and want to move it from a chaotic mode into a clear project rhythm.
A 2–5 person project
When there is already an engineer, a manager, and perhaps another developer or tester, and everyone needs to work within one contour.
The first management layer
Suitable for leads and initiators who need not only to write code, but also to gather a team and synchronize actions.
An early commercial initiative
Appropriate for small teams that have already reached the pilot stage, but have not yet moved into a heavy service or infrastructure mode.
Team is bought not for power, but for manageability
If the main pain point is organizing people and shared projects, Team addresses it best. But if the bottleneck is already heavy builds, high priority, or professional support, the next step is Build+ or Support.