Skip to content
STIRUP

TECHNOLOGY INTELLIGENCE

Understand what's next.

Open-Source Chatbase Alternative's Technical Setup and Dependencies

The open-source Chatbase alternative uses Next.js, React, Tailwind CSS, Supabase, and AI models like Claude, Gemini, and GPT for its technical implementation and integrations.

Share
AI-generated conceptual illustration accompanying: Open-Source Chatbase Alternative's Technical Setup and Dependencies
AI-generated editorial illustration of the article topic; not a photograph, product screenshot or measured result.

Technical Implementation and Dependencies

The technical implementation of this open-source Chatbase alternative relies on a combination of modern web development tools and third-party services. Built with Next.js, React, and Tailwind CSS, the platform leverages Supabase for its Postgres database, including pgvector for vector similarity searches and user authentication. For AI integration, it utilizes Claude, Gemini, and GPT through the Vercel AI SDK, while Gemini and ElevenLabs are employed for speech-related features. Additional services like Stripe, Resend, and Upstash support payment processing, email delivery, and caching, respectively.

Users can run the application locally by installing Node 22 or newer, Docker, and the Supabase CLI. The setup process involves running npm install, initializing a local database with supabase start, configuring environment variables with cp .env.example .env.local, and launching the app with npm run dev at http://localhost:3010. For local testing, sign-in codes are sent to Mailpit at http://127.0.0.1:55424 instead of a regular email inbox.

Self-Hosting and Local Setup Requirements

To set up the open-source Chatbase alternative locally, users must first install Node 22 or newer, Docker, and the Supabase CLI as outlined in the local setup instructions (Hacker News Show). The process begins with running supabase start to initialize a local database. Next, users should copy the example environment file with cp .env.example .env.local and input their API keys. The application can then be launched using npm run dev, which starts the service at http://localhost:3010 (Hacker News Show). For local authentication, sign-in codes are sent to Mailpit at http://127.0.0.1:55424 instead of the user's actual inbox. Additionally, users must generate two random strings for WIDGET_SESSION_SECRET and ENCRYPTION_KEY, which can be created using a command like openssl rand -hex 32 (Hacker News Show).

Integration with Third-Party Services

Integration with third-party services is a core feature of the open-source Chatbase alternative with voice. Users can post to Slack, open tickets in Zendesk, Salesforce, or HubSpot, save leads, and book meetings with Cal.com or Calendly. Each service assigns the assistant a specific job, such as telling the team when to step in via Slack or opening a ticket in Zendesk. Setup for each service typically involves connecting through OAuth, an API key, or both. For example, Cal.com allows customers to paste an API key, which also works with self-hosted instances of Cal.com. These integrations enable seamless automation and collaboration across platforms without requiring custom development.

OAuth and Authentication Setup

Setting up OAuth and authentication in an open-source Chatbase alternative with voice requires careful configuration of client credentials and redirect URIs. According to Hacker News Show, developers should place a Google OAuth client's ID and secret in the .env file (not .env.local) and add http://127.0.0.1:55421/auth/v1/callback as a redirect URI before restarting Supabase. For a Connect button, Hacker News Show specifies creating an OAuth client with the scopes PROFILE_READ, EVENT_TYPE_READ, BOOKING_READ, and BOOKING_WRITE, then setting CALCOM_CLIENT_ID and CALCOM_CLIENT_SECRET. Similarly, Hacker News Show outlines creating an OAuth client with the scopes users:read, event_types:read, and scheduled_events:write, followed by setting CALENDLY_CLIENT_ID and CALENDLY_CLIENT_SECRET. These steps ensure secure and functional authentication integration.

Licensing and Open-Source Compliance

Oriel is open source under the AGPL-3.0 license, which applies to both the software and the hosted service's billing and marketing site, as noted in Hacker News Show. This license requires that if users modify Oriel and deploy it as a service for others, they must share their source code with those users, according to Hacker News Show. The platform currently supports up to 25 accounts before requiring listing on HubSpot's marketplace, as stated in Hacker News Show. These licensing terms ensure transparency and compliance for developers and businesses using or distributing Oriel. Users should carefully review the AGPL-3.0 terms to understand their obligations when deploying modified versions of the software.

Sources and reporting notes

Based on published source material. No independent hands-on testing is claimed.

Read more