Skip to main content

Bike4Mind – Client Documentation

This documentation is for enterprise customers, IT administrators, and client success stakeholders of the Bike4Mind platform.

1. Platform Overview​

  • Unified AI research, notebook, and agent development platform
  • Built on open technologies (React, Node, MongoDB, AWS)
  • Delivered either SaaS or deployed into your own AWS environment
  • "Batteries Included" setup with full tooling and dashboards

2. Authentication​

  • Supports enterprise OAuth (Okta, Google, GitHub)
  • Secure JWT token-based session management
  • Token rotation and refresh for improved session integrity
  • Fully auditable login/logout and session data available via admin tools

3. Access Control​

  • Role-based system for granular access:
    • Admin
    • Org Admin
    • Team Member
    • Guest
  • Share resources (Notebooks, Files, Prompts) across teams or globally
  • Create system prompts with weight and priority

4. Projects and Sharing​

  • Bundle resources into "Projects"
  • Assign visibility: 1:1, 1:group, 1:org, public
  • Track shared resources with feed-style profile pages
  • Control sharing through admin panel and access scopes

5. Data Sovereignty & Compliance​

  • Region-specific hosting (via AWS)
  • Optional full-source license for in-house deployment
  • Deploy into customer-controlled AWS accounts
  • Security aligned with CIS Benchmarks and AWS Well-Architected Framework

6. Operational Insights​

  • Real-time dashboards show platform and usage stats
  • Daily/weekly reports (email + Slack)
  • AI-generated TL;DR summaries for insights
  • Built-in analytics dashboard (no third-party tools required)

7. Governance & Admin Tools​

  • Admin panel includes:
    • Feature toggles
    • Usage telemetry
    • User tagging & management
    • File and prompt visibility controls
  • Custom themes and logo for brand alignment

8. Support & SLAs​

  • Dedicated client success manager
  • Slack or email-based communication
  • Prioritized issue handling:
    • P0: Critical – immediate response
    • P1: Priority – deploy as soon as possible
    • P2: Normal – 10–60 days
    • P3: Idea backlog – tracked, but not scheduled
  • Transparent roadmap and changelogs

9. Onboarding & Co-Development​

  • Onboarding sessions with product team
  • Optional co-development model
  • Shared Slack channel for real-time collaboration
  • Optional training and documentation handoff