Better Auth Ruby

A modern authentication framework for Ruby, inspired by Better Auth.

This project is independent and is not affiliated with, maintained by, or endorsed by the Better Auth project.

Ruby server packages for Better Auth. The core is Rack-first, with adapters for Rails, Sinatra, and Hanami, plus Ruby packages for selected Better Auth plugins.

Documentation - Supported features - Upstream Better Auth - Issues

Current upstream target: Better Auth v1.6.9.

This project is active work. The Ruby port implements a large server-side surface, but exact upstream parity is still being tightened across some routes, adapter edge cases, OpenAPI schemas, and docs pages.

# Gemfile
gem "better_auth-rails"

bundle install
bin/rails generate better_auth:install

# config/routes.rb
Rails.application.routes.draw do
  better_auth
end

# Gemfile
gem "better_auth"

require "better_auth"

auth = BetterAuth.auth(
  secret: ENV.fetch("BETTER_AUTH_SECRET"),
  base_url: "http://localhost:3000",
  database: BetterAuth::Adapters::Memory.new
)

run auth

# Gemfile
gem "better_auth-sinatra"

require "sinatra/base"
require "better_auth/sinatra"

class App < Sinatra::Base
  register BetterAuth::Sinatra

  better_auth at: "/api/auth" do |config|
    config.secret = ENV.fetch("BETTER_AUTH_SECRET")
    config.base_url = ENV.fetch("BETTER_AUTH_URL")
    config.database = ->(options) {
      BetterAuth::Adapters::Postgres.new(options, url: ENV.fetch("DATABASE_URL"))
    }
  end
end

# Gemfile
gem "better_auth-hanami"

bundle install
bundle exec rake better_auth:init
bin/hanami db migrate

See the docs page for the current support inventory:

• Supported Features
• Local feature notes
• Implementation plans

Short version:

• Rack core, Rails, Sinatra, and Hanami integration packages exist.
• Email/password, sessions, social OAuth, database adapters, and many server plugins are implemented with Ruby tests.
• Payment docs and navigation only list Stripe. Other upstream payment plugins are intentionally not marked as supported.
• Browser client packages and TypeScript-only helpers are outside the Ruby server scope unless a Ruby package explicitly documents an equivalent.

• better_auth: Rack core, auth routes, sessions, cookies, adapters, plugin system, and built-in server plugins.
• better_auth-rails: Rails mount helpers, ActiveRecord adapter, controller helpers, migrations, and generators.
• better_auth-sinatra: Sinatra extension, Rack mounting, helpers, and migration tasks.
• better_auth-hanami: Hanami integration, action helpers, Sequel adapter, migrations, and generators.
• better_auth-mongo-adapter: MongoDB database adapter.
• better_auth-redis-storage: Redis secondary storage.
• better_auth-api-key: API key plugin package.
• better_auth-passkey: Passkey/WebAuthn plugin package.
• better_auth-oauth-provider: OAuth 2.0/OIDC provider plugin package.
• better_auth-scim: SCIM v2 provisioning plugin package.
• better_auth-sso: OIDC and SAML SSO plugin package.
• better_auth-stripe: Stripe billing plugin package.

OpenAuth alias packages are also available for users who prefer that naming. They install and load the matching Better Auth Ruby packages, and their READMEs point back to the canonical documentation at https://better-auth-rb.vercel.app/.

• openauth: Alias for better_auth.
• openauth-rails: Alias for better_auth-rails.
• openauth-sinatra: Alias for better_auth-sinatra.
• openauth-hanami: Alias for better_auth-hanami.
• openauth-mongodb: Alias for better_auth-mongo-adapter.
• openauth-redis-storage: Alias for better_auth-redis-storage.
• openauth-api-key: Alias for better_auth-api-key.
• openauth-passkey: Alias for better_auth-passkey.
• openauth-oauth-provider: Alias for better_auth-oauth-provider.
• openauth-scim: Alias for better_auth-scim.
• openauth-sso: Alias for better_auth-sso.
• openauth-stripe: Alias for better_auth-stripe.

git clone --recursive https://github.com/sebasxsala/better-auth.git
cd better-auth
make install
make ci

Run a single package:

cd packages/better_auth
bundle exec rake test

Database-backed tests may require the repo services:

docker compose up -d

1. Branch from canary.
2. Read AGENTS.md and the package-specific instructions before editing a package.
3. Check upstream source and tests for behavior changes.
4. Run the relevant package tests, or make ci for the full repo.
5. Open a PR to canary.

Report vulnerabilities to security@openparcel.dev. See SECURITY.md.

MIT License