Product Direction

Understand Provisionr’s product direction, focus areas, supported integrations, target market segments, and how we prioritize features for policy-based access control.

See our Product Mission for more details about our overall mission and vision.

Feature Request Philosophy

We all have a lot of great ideas, however we can’t do everything for everyone. We are all familiar with constraints and trade offs, and we are deliberate with what we choose to build and if/when we are ready to build it.

By focusing on group membership on a few core systems with large ecosystems, our customers (hopefully that’s you?) can use those groups in downstream systems to manage access without us trying to boil the ocean with hundreds of integrations. This allows you to get up and running quickly using the systems and integrations that you’re already using.

If a resource has membership that behaves similar to groups, we may consider adding supporting if those resources are something that our customers are already using heavily and need better access management for them.

Workforce IAM Landscape

We have mapped out the broader Identity and Access Management landscape to illustrate where Provisionr fits in relation to other solutions and technologies.

As organizations and IT teams evaluate identity and access management solutions, it’s important to understand the different categories and pillars that make up the overall landscape. This helps in identifying which solutions align with specific needs and goals.

Focus Areas

This is our sticky note wall of what’s in scope, viable for future consideration, and out of scope for our product direction.

This is an idea board, not a commitment that we will build everything listed as In Scope or Future Consideration. We are simply transparent with our list of interesting ideas to guide our decisions about what to prioritize based on our mission and customer needs.

See our Release Schedule for what we have committed to that you’ll see soon.

See our Wishlist for ideas that have graduated from a sticky note to a GitLab issue that needs additional evaluation to determine viability.

Category	In Scope	Future Consideration	Out of Scope
Identity & Resource Integrations	AWS Identity Center GitLab Google Cloud (GCP) Google Drive Google Workspace Okta Slack	Auth0 Clerk Microsoft Entra ID (IdP import only) One Login Ping Identity PropelAuth WorkOS	AWS Resources Microsoft Azure Microsoft Entra MyApps Microsoft Office 365 Microsoft OneDrive SAP SuccessFactors
HRIS Identity Sources	We are focused on Google Workspace and Okta user profiles as our primary identity source. You can connect your HRIS user profile data in Google or Okta	BambooHR ChartHop Deel Gusto Humaans Namely Rippling Workday	ADP Ceridian SAP SuccessFactors
Identity Types	Employee Users Contractor Users 3rd Party Customers 3rd Party Partners 3rd Party Vendors Group Members	AI Agents App Assignments	Infrastructure Identities Service Accounts Workload Identities
Compliance Frameworks	CIS GDPR ISO 27001 NIST CSF 2.0 NIST 800-53 NIST 800-63 NIST 800-171 SOC1 SOC2 SOX	FedRAMP HIPAA ISO27017 ISO 27701
Management Interfaces	APIs CLI Client No Code Workflows Terraform Provider Web UI	Email Reply Approvals Helpdesk Integrations iOS App Programming Language SDKs Slack Bot Commands	Android App macOS App Windows App
Automation Areas	Policy-based Access Control (PBAC) Attribute-based Access Control (ABAC) Role-Based Access Control (RBAC) Provisioning & Deprovisioning Access Requests Role Mining	Access Reviews Access Certifications Segregation of Duties Just-in-Time Access Ephemeral Elevated Access
Access Context	HRIS Data User Identity Group Memberships	Device Trust Location	Time of Day Network
Deployment Models	Cloud SaaS	Hybrid Cloud	On-Premises
Customer Segments	Small Businesses Mid-Market companies (up to 5,000 employees) Tech companies up to 20,000 employees		Government Agencies Highly Regulated Industries (case-by-case approval) Organizations with 20,000+ employees
Integration Protocols	REST APIs OAuth 2.0	MCP SCIM SAML	LDAP SOAP RPC GraphQL SQL FTP CSV
Operating Systems	macOS (Arm)	Linux (popular distros) iOS	Windows Legacy macOS (Intel) Android
Support Channels	Business Hours Support Email Tickets Professional Services Slack Community Support Tickets Zoom	24x5 SLA Support Phone Support Dedicated Account Manager	In-Person Support On-Site Visits Resident Engineers

Decision Criteria

Less is More

We care deeply about our craft and prefer to do a few things exceptionally well.

We can always say no today and say yes in the future. It’s harder to say yes to everything and then backtrack after we’ve overcommitted ourselves. We also don’t want to put you in that awkward situation and have false expectations.

Nobody wants bloatware and frankenstein products, but it takes intention to build something elegant and focused. So we’re sorry if we disappoint you by not building everything you’d like to see, but we hope you understand our reasoning.

Tech Stack Fit

There may be market segments that we don’t have ambitions to serve.

We have a strong ethos of serving the people that are doing the jobs that we’ve done before, so we can apply what we’ve learned to help them. If we haven’t done it, we’re not going to fake it. We’re going to scratch our itch and optimize it in a way that helps as many people as possible who are in the same boat.

Target Market Segment

Our core customer focus is organizations that are using Google Workspace and/or Okta for identity and access management. Our founder and leadership team were system administrators of those systems so we feel and have lived your pain.

There are some vendors that we might not integrate with, but it’s still viable to build your own integrations. We are API first, so if you can use our APIs to build your own solution, great. If you can’t make it work, we’re okay not being the right fit for you. We’re not going to try to support a round peg in a square hole. We’re happy to refer you to one of our competitors who might be able to help.

While we plan to integrate with Microsoft Entra ID for importing identities for user profile data, we do not plan to build deep integrations with Microsoft Azure or other Microsoft products. The Microsoft ecosystem is vast and complex, and it requires a different product architecture and philosophy that would require breaking the elegant approach for the other vendors that we integrate with. There are many other tools on the market that can solve similar problems, including Microsoft Entra governance features like Entitlement Management.

Competitor Differentiation

Some of our larger competitors have built 747 cockpits with every knob and switch to cater to complex scenarios. We’re happy to let them handle the top 20% of edge cases while we keep our sanity and help our customers that need simpler solutions that cover the other 80%. Our implementation time is measured in hours, theirs is in months, so it’s a different scale of difficulty.

We’re building a Cessna with a vision of becoming a Gulfstream that both pilots (that’s you) and passengers (your users) love. Smaller yet beautiful planes, simpler operation than a big airline, and we’re okay with that. Everyone does a good day’s work, enjoys the scenic flight, and gets to sleep peacefully in their own bed every night.

Identity Governance and Administration is a broad and complex domain, and we’re okay with not trying to boil the ocean. We know what we do well, and we want to help the everyday heroes (that’s you) that need an easy to implement solution to get the job done without a massive learning curve or months of onboarding.