PM Corp is a company providing strategy and logistics for intergalactic missions. We are an API-first company, providing the next generation of digital resources, capabilities, and experiences across a variety of industries looking to lead business expansion into space. To manage our operations, we employ eleven separate workspaces to meet the daily needs across our operations, with three levels of visibility.
- Engineering Onboarding Workspace (Discussion) - A workspace for providing team members with what they need to begin working with engineering APIs.
- Engineering Reference Workspace (Discussion) - A workspace for providing developers with a reference implementation showing what ideal API practices look like.
- Infrastructure Workspace (Discussion) - A workspace for providing DevOps/IT with what they need to manage their work across operations.
- Developer Workspaces (Discussion) - A workspace for managing everything involved with producing an API.
- Testing Workspace (Discussion) - A workspace providing a testing area for QA teams to validate and test APIs.
- Incident Response Workspace (Discussion) - Collaborative troubleshooting when something goes wrong and systems are down
- Support Workspace (Discussion) - Troubleshooting when something goes wrong for a specific partner, customer, or community.
- Sales Workspace (Discussion) - Providing sales teams with a variety of collections to provide them with the data and visualizations they need to support their deals.
- Security Workspace (Discussion) - Providing a central place that supports all the security needs of API being produced or consumed.
- Demo workspace (Discussion) - A place for solution/sales/marketing engineers to show how an API works.
- Public API Workspace (Discussion) - A workspace dedicated to meeting the needs of a public API.
PM Corp depends on APIs to deliver what our customers need, and we depend on these eleven workspace use cases to produce APIs but also engage with internal, external, and public API consumers, as well as manage our own consumption of partner and 3rd party APIs that we depend on.