We recently launched our Parsec for Teams API, making key admin functionality open & accessible to organizations who need it. It’s a big step on answering a question we’ve been kicking around and bringing up in conversations with our incredible community of customers:
How do we get Parsec to scale with a company’s needs without sacrificing performance, overcomplicating the experience, or bloating up our app?
Companies are using Parsec to not just power day-to-day work, but also run digital events, scale user research teams, and spin cloud hardware up around the world. And we also serve millions of people using Parsec every single day to connect with a friend, or play a game on the go.
These pretty divergent use cases could set you off in two directions. Design a product with hundreds of microservices that do an ok job at hundreds of different use cases. Or design a product that does what it does incredibly well, and let the experts (the customers) build the particular services they need for their particular use case.
Right now, we’re choosing the latter. Keep Parsec small, and let you make it do anything you want it to do.
Parsec For Your Particular Team
Documentation wise the API is pretty straightforward: everything a Parsec for Teams admin can do, an API application can do. For the uninitiated, here are some of those core functions:
Invite & Manage Members: Only people invited to a team can connect to the computers & other members of that organization. Keep it secure.
Groups: Once added to a team, groups let you organize team members with others who need to frequently connect to each other, access the same machines, or need common permissions.
Team Computers: Computers can be provisioned so they’re always associated with your team. Individuals or groups can be assigned access to those machines.
Guest Access: If you don’t need to add someone to your team forever, guest access allows you to invite people outside your team to use a computer for a finite period of time.
All seems pretty simple, right? For many organizations, these features on their own will do their job just fine.
But when you start thinking through when Parsec is used for big, scaled workflows, you can start to see where the API fits in.
Using the Teams API, an admin could automate inviting, organizing, assigning, and permissioning a new employee’s computer, so that when it’s day one on the job, all they have to do is open Parsec and they’re off to work. And they could do so at scale.
Another one: a gaming conference could build an application that sends out thousands of highly branded, customized invites to play demos during a remote activation. They could even build a system to let people sign up for certain time slots, and automate access for narrow time windows.
Instead of asking a customer to learn a system Parsec invents, we want customers to invent systems on top of Parsec. And we can’t wait to see what they come up with.
A Whole Lot More Than Remote Desktop
We think the possibilities in a Parsec API are pretty much endless. Low latency access to basically any computer on Earth makes it possible to rebuild workflows and experiences that previously only ever worked in-person.
The API is available as an upgrade to Parsec for Teams, and comes packaged with our high performance relay (another great tool for big orgs).
If you’re interested, fill out this form and let us know. We’re going to be building even more great tooling for large orgs to build Parsec into existing systems, and we’ll be happy to tell you all about ‘em.