KnowledgeBricks replaces zero systems. It runs on top of your existing identity provider, billing infrastructure, and data sources. Every integration is production-grade, documented, and enforced server-side, not wired together with brittle webhooks.
Authentication is handled by Clerk, one of the most widely deployed auth platforms for modern SaaS applications. Out of the box, KnowledgeBricks supports email/password, Google OAuth, Microsoft OAuth, and magic-link sign-in. For enterprise and team deployments, SAML-based SSO connects to Okta, Azure AD, and any standards-compliant identity provider.
Access tier assignment is propagated from Clerk session metadata on every server-side request. Role changes take effect immediately, no cache invalidation lag, no eventual consistency gaps. An admin demoting a user from Principal to Associate tier sees that change enforced on the next query, not the next login.
Custom portals ingest your organization's internal knowledge through the same five-layer pipeline as the standard portals, with additional data connectors for enterprise document sources. SOPs from SharePoint, operational runbooks from Confluence, bid templates from Google Drive, master data from your ERP, all transformed into queryable knowledge.
Ingestion is not a one-time import. We schedule recurring sync jobs against your sources so the knowledge base reflects your current operations, not a snapshot from 18 months ago. New documents are automatically classified, chunked, embedded, and made available to your team without manual intervention.
Clerk manages all session lifecycle. SAML 2.0 SSO for enterprise. Google and Microsoft OAuth for SMB teams. MFA available on all plans. Zero passwords stored in KnowledgeBricks infrastructure.
Stripe handles all subscription management, seat-based billing, and payment processing. Plan gating is enforced server-side via Stripe subscription metadata, not UI flags that can be bypassed.
Dual LLM architecture: OpenAI text-embedding-3-large for embeddings, Anthropic Claude Sonnet for answer generation. Model selection is configurable per portal. Both providers are SOC 2 compliant.
Supabase PostgreSQL with pgvector extension handles both relational data and vector embeddings in a single SOC 2 Type II compliant platform. Row-level security enforces portal data isolation at the database layer.
PostHog provides product analytics for query patterns, session depth, feature usage, and content gap identification. All analytics data is anonymized before transmission. No PII in event payloads.
Transactional email via Resend: account activation, password resets, billing notifications, and admin alerts. Custom domain sending available for white-label custom portal deployments.
Custom portal builds start with a data inventory call. We identify your highest-value knowledge sources, assess document quality and format, and design a collection architecture that pulls the right content without granting over-broad access to your systems.
We collect SOPs, runbooks, training materials, bid templates, and methodology documents. Any format, PDF, Word, Excel, HTML, Markdown. Legacy scanned documents handled via OCR pipeline.
ERP item masters, WMS rate cards, TMS lane data, and supplier databases are exported via API or scheduled flat-file. Structured data is formatted into queryable knowledge entries, not raw database rows.
Confluence, Notion, and SharePoint wiki spaces are connected via API with read-only service accounts. Sync schedules are configurable, daily refresh for stable reference content, hourly for active operational data.
The knowledge base is not a one-time import. We maintain ingestion pipelines, retire outdated content when sources are updated, and flag knowledge gaps identified by user query patterns.
A scoping call covers your existing stack, identifies integration points, and produces a data architecture plan for your custom portal, or confirms a standard portal fits your needs out of the box.
Standard portal integrations are pre-built. Custom portal data connectors scoped during onboarding.