KebecDB

A modern SQLite database platform designed for developers who need a powerful, self-contained database solution without the complexity of traditional database servers. KebecDB combines the simplicity and reliability of SQLite with enterprise-grade features like automatic S3 replication, a built-in REST API, visual administration tools, and AI integration.

Built on SQLite's Write-Ahead Logging (WAL) mode and featuring an intelligent write queue system, KebecDB delivers high-performance concurrent reads while maintaining data consistency through batched write operations. Whether you're building a web application, mobile backend, or desktop software, KebecDB provides everything you need out of the box: auto-generated CRUD endpoints, a comprehensive admin interface with SQL console, custom edge functions, and seamless integration with AI agents through the Model Context Protocol (MCP).

KebecDB works as a drop-in solution for modern JavaScript frameworks including Next.js, Nuxt, SvelteKit, Astro, Angular, and Solid, making it the perfect choice for developers who want a production-ready database that just works.

Features

• SQLite WAL Mode - High-performance concurrent reads
• Write Queue - Batched writes for optimal throughput
• REST API - Auto-generated CRUD endpoints
• Admin UI - Visual table management and SQL console
• MCP Server - AI agent integration
• Custom Routes - User-defined edge functions
• Litestream - Automatic S3 replication
• Multi-framework - Works with Next.js, Nuxt, SvelteKit, Astro, Angular, Solid

Quick Start

# Install
bun add kebecdb

# Initialize
npx kebecdb init

# Start
npx kebecdb start

Publishing

To publish a new version to npm:

1. Setup your NPM token (first time only):

   cp .env.example .env

   Then edit .env and add your NPM token:

   NPM_TOKEN=npm_your_token_here

2. Publish:

   # Windows
   scripts\npm-publish.bat
      
   # Unix/Linux/macOS
   bun run scripts/publish.ts

The script will:

• Prompt you to select version bump type (patch, minor, major, pre-release, or custom)
• Update package.json with the new version
• Read your token from .env
• Create a temporary .npmrc
• Publish to npm
• Commit and push the version bump
• Clean up the temporary file

Note: .env is gitignored and never committed.

Documentation

• Architecture
• API Reference
• Implementation Plans
• Architecture Decisions

License

MIT