Digest and serve HTML asset files

Rack middleware for Datadome.

Format data for display

A Ruby gem with a C extension for high-performance scanning and redaction of 85 sensitive patterns — API keys, tokens, credentials, IBANs, national IDs, emails, phone numbers, and PII from 15+ countries. Optional Logger formatter, Rails filter_parameters adapter, and Rack middleware. Designed to sanitize text before sending to LLMs, logging systems, or any public/third-party API.

Rack compatible user authentication microservice. Can be run standalone or mounted into another rack app.

Agile Interface on top of SQL Databases

Use DBEnvy to parse DATABASE_URL and shim the info into a database.yml

Allows a single Rails appliation to access many different databases

Behaviour Driven Development for Ruby on Rails.

Handler-based web framework powered by Sinatra

Replay HTTP requests, ActiveJob jobs, ActionMailer deliveries, and Rake tasks with hot-reloaded code at debugger breakpoints.

A production-grade decision agent that provides deterministic rule evaluation, conflict resolution, and full audit replay capabilities. Framework-agnostic and AI-optional.

Access controll by IP Address.

Delayed Job Promtheues Metrcis

The Deltacloud API is built as a service-based REST API. You do not directly link a Deltacloud library into your program to use it. Instead, a client speaks the Deltacloud API over HTTP to a server which implements the REST interface.

Add simple password protection for demo Rack apps.

Denouncer allows you to send notifications with error/exception details using a simple interface. New methods of sending error messages can be implemented using a pre-defined class interface. SMTP and AMQP notification are the first implemented adapters. Denouncer is usable for all ruby applications, Rails is not required. Use denouncer to get informed on error occurences instantly.

A rack middleware layer that logs the full request cycle.

CLI to interact with Heroku's Dev Center

A standalone Rack Middleware application that authenticates a username/password against a devise-powered backend application before forwarding the original HTTP request to the same application. Authentication is done on *every* request, so it is advisable to use devise-proxy sparingly.