Use Oblive
Install the local stack, onboard an organization, connect its tools, and operate durable work.
Use this section to move from a fresh checkout to an active organization with inspectable context, bounded integrations, durable tasks, scheduled work, and explicit human checkpoints.
Getting Started
Check requirements, configure the local stack, start every service, and verify health.
Onboard an Organization
Prepare business sources, upload or write context, resolve evidence gaps, and activate.
Operate Oblive
Use chat, tasks, the Human Inbox, Context, and schedules during day-to-day operation.
Connect Integrations
Configure managed providers, Google Workspace, custom MCP servers, and access policy.
Configuration
Understand local-stack fields, generated environments, authentication, and secrets.
Troubleshooting
Diagnose stack startup, storage, onboarding, runtime, and integration failures.
Recommended Order
Start the stack
Follow Getting Started and verify the frontend, backend, infrastructure, chat, and workers before creating an organization.
Onboard one organization
Provide current organization and department sources, answer evidence-specific questions, and review the compiled context before activation.
Connect only required tools
Begin with the narrowest useful services, tools, profile grants, and access mode.
Run bounded work
Start with a clear outcome and verification method, then inspect task attempts, questions, actions, artifacts, and receipts.
Supported Scope
The documented setup is local-first and self-hosted. It includes the Oblive frontend and backend, PostgreSQL with pgvector, Redis, Garage-compatible object storage, chat and worker runtimes, and the Growth, Engineering, and Support department profiles.
For repository changes, use Develop. For request and response contracts, use the API Reference.