ɳSelfɳSELFDOCS

  • Getting Started

    • Introduction
    • Quick Start
    • Installation
    • Your First Project

  • Core Concepts

    • Architecture Overview
    • Project Structure
    • Configuration
    • Environments

  • Services

    • PostgreSQL Database
    • Hasura GraphQL
    • Authentication
    • Real-Time Communication
    • Storage (MinIO)
    • Email Configuration
    • Redis Cache
    • Search Engines
    • Functions
    • MLflow (ML Tracking)
    • Monitoring & Metrics
    • Admin UI
    • Dashboard

  • Database Tools

    • Schema Management
    • Migrations
    • Seeding Data
    • Backup & Restore
    • dbdiagram.io Sync

  • Microservices

    • NestJS Services
    • BullMQ Workers
    • Go Services
    • Python Services

  • CLI Reference

    • All Commands
    • Core Commands
    • Database Commands
    • Service Management
    • Production Commands

  • Deployment

    • Local Development
    • Production Setup
    • SSL/TLS Configuration
    • Domain Configuration
    • Environment Variables

  • Advanced Topics

    • Multi-Tenancy & SaaS
    • Security & Hardening
    • Custom Actions
    • Webhooks
    • Performance Tuning
    • Troubleshooting

  • ɳClaw

    • Backend Manager
    • API Gateway
    • Voice Input
    • Threads & Projects

  • Migration Guides

    • From Supabase
    • From Nhost
    • From Firebase

  • Plugins

    • Plugin catalog (87)
    • Installation
    • Free plugins (25)
    • Pro plugins (62)

  • Reference

    • Stack & Hosting
    • API Reference
    • Guides
    • RFCs
    • Legal
    • Contributing

  • Resources

    • Changelog
    • Licensing
    • FAQ
    • Support

RFCs

Significant design changes go through a public RFC. This page lists accepted, in-review, and draft RFCs. Source lives in the cli repo under docs/rfcs/.

How to propose an RFC

  1. Open an issue titled RFC: <topic> describing the problem and proposed design.
  2. Wait for triage. Small changes are handled in a regular PR. Significant changes get an RFC number.
  3. Open a PR adding docs/rfcs/NNN-topic.md following the template.
  4. Address review comments. RFCs land when at least two maintainers approve.

Current RFCs

IDTitleStatusUpdatedSummary
001Plugin manifest v2Accepted2026-02-10Structured plugin.json schema with tier, permissions, and service bindings.
002License tier cascadeAccepted2026-03-05Seven-tier pricing with additive plugin access. Existing keys grandfather.
003Go CLI rewriteShipped v1.0.62026-03-29Replace Bash CLI with single Go binary. Four platform targets.
004Remote Schema registryIn review2026-04-12Namespaced Remote Schemas per app with auto-registration on plugin install.
005Backup encryptionDraft2026-04-15Client-side encrypted backups with age-based key rotation.

Related

  • Contributing guide
  • CLI reference