Basedash is enterprise ready now
We just shipped SCIM provisioning (check it out!) and it got me reflecting on how much enterprise infrastructure we've built over the past year.
When we started selling upmarket, our answer to most security questionnaire items was "not yet." Today the checklist looks pretty different:
SSO (SAML and OIDC): authenticate through the identity provider your company already uses
SCIM provisioning: users, groups, and memberships sync automatically from Okta or Entra as people join, move teams, or leave
RBAC: groups with fine-grained permissions on data sources, dashboards, chats, automations, and MCP servers
Row-level security: control which rows each person can see, and the AI respects those policies in every query it runs
SOC 2 Type II: audited annually, encryption in transit and at rest
Audit logs: who accessed what data and when
Self-hosting: deploy in your own network with Docker or Kubernetes, bring your own AI model keys, and align with HIPAA, ISO 27001, GDPR, or PCI-DSS requirements
And across all of it: your data is never used to train models.
The interesting part is how these layers fit together. Your IdP decides who belongs, SCIM carries that into Basedash, RBAC decides what they can touch, and RLS decides which rows they see. Identity stays in one place instead of becoming another thing your data team manages by hand.
Honestly, none of these features are "fun" to build. But they're the difference between a cool AI demo and something a 5,000-person company will actually roll out.
If you're evaluating Basedash and security review is your next step, happy to answer anything here. What else would you want to see on this list?


Replies
Great job on the progress with Basedash!!
We are prepping for our CASA assessment currently for our Gmail integration within Salestrics.