rage-rb.dev valid

Rage Framework Documentation

Comprehensive guide to building applications with the Ruby Rage framework

For agents: Documentation for Rage, a Ruby web framework: API reference, release blog and WebSocket support (Action Cable-compatible).

ruby frameworkrage frameworkwebsocketsaction cableruby web development

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T10:15:08.236Z. Cached copy · Source on rage-rb.dev

# Rage Framework Documentation

> Comprehensive guide to building applications with the Ruby Rage framework


## Api

- [API Reference](https://rage-rb.dev/api.md): Complete technical documentation for all Rage framework classes and modules.

## Blog

- [Blog](https://rage-rb.dev/blog.md): Blog
- [Version 0.1 Release](https://rage-rb.dev/blog/2023/09/15/version-0-1.md): Today marks the first official release of Rage. This initial version includes the foundational pieces:
- [Version 0.7 Release](https://rage-rb.dev/blog/2024/01/09/version-0-7.md): Version 0.7 is a significant milestone - all the features planned for the initial release are now implemented. The framework has the essential pieces in place:
- [WebSocket Support](https://rage-rb.dev/blog/2024/08/06/websockets.md): Version 1.8.0 adds WebSocket support through an Action Cable-compatible API. If you're familiar with Action Cable, the interface will feel immediately familiar - same channels, same broadcasting patterns.
- [OpenAPI Documentation](https://rage-rb.dev/blog/2024/12/18/openapi.md): Version 1.11.0 brings Rage::OpenAPI for API documentation. The goal was to make documenting APIs less painful - you document your APIs using YARD-style tags, and it generates OpenAPI 3.0 specs automatically.
- [TechEmpower Benchmarks](https://rage-rb.dev/blog/2025/03/11/techempower-benchmarks.md): TechEmpower Round 23 results are in. Rage shows solid performance improvements over other Ruby frameworks:
- [Rage REST API Tutorial](https://rage-rb.dev/blog/2025/04/13/zuplo-tutorial.md): We collaborated with Zuplo on a tutorial for building REST APIs with Rage. The guide walks through creating a full-featured API application from scratch:
- [Cloudflare Support](https://rage-rb.dev/blog/2025/07/17/cloudflare-support.md): Rage was accepted into Cloudflare's Project Alexandria today.
- [Background Tasks](https://rage-rb.dev/blog/2025/08/20/deferred.md): Version 1.17.0 introduces Rage::Deferred for background task execution.
- [Impractical Ruby Optimisations](https://rage-rb.dev/blog/2025/09/30/impractical-ruby-optimisations.md): Wrote an article exploring some unconventional performance optimizations in Ruby.
- [Observability Features](https://rage-rb.dev/blog/2026/01/23/observability.md): Versions 1.19.0 and 1.20.0 brought a set of observability features designed to make debugging and monitoring Rage applications easier. The focus was on giving you control over your logs and visibility into what's happening inside the framework.
- [The Operational Monolith](https://rage-rb.dev/blog/2026/02/20/operational-monolith.md): Wrote an article exploring what Rails might look like if it was designed around modern operational constraints from day one.
- [SSE Benchmark](https://rage-rb.dev/blog/2026/04/09/sse-benchmark.md): Ran a benchmark to test SSE performance under sustained load. Two workers on a €12/month CCX13 Hetzner server handling 5K RPS to a SQLite-backed endpoint plus 5K concurrent SSE streams.
- [Producti
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=rage-rb.dev · GET /v1/domain/rage-rb.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for rage-rb.dev:
1. POST https://agentwebmap.com/v1/sites/rage-rb.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://rage-rb.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/rage-rb.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/rage-rb.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.