railseventstore.org valid

Rails Event Store

Rails Event Store (RES) is an open-source library for Ruby and Rails for publishing, consuming, storing, and retrieving events. It helps applications adopt event-driven architecture and decouple business logic.

For agents: Open-source Ruby/Rails event store library for publishing, storing and subscribing to domain events; includes getting-started and API docs.

ruby on railsevent sourcingevent-driven architecturedomain eventsruby gem

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T00:41:37.523Z. Cached copy · Source on railseventstore.org

# Rails Event Store

> Rails Event Store (RES) is an open-source library for Ruby and Rails for publishing, consuming, storing, and retrieving events. It helps applications adopt event-driven architecture and decouple business logic.

RES can be used as a publish-subscribe bus, an alternative to ActiveRecord callbacks, an audit log, and a foundation for read models and event sourcing. Event handlers can run synchronously or asynchronously. Event sourcing is one use case, not a requirement for using RES.

The project is funded and maintained by Arkency and released under the MIT license. Ruby Event Store can also be used without Rails.

The documentation links below use the default published version. For version-specific API details, select the documentation version matching the application's gems; `/docs/master/` covers development rather than a published release.

## Getting started

- [Homepage](https://railseventstore.org/): Project overview and use cases.
- [Introduction](https://railseventstore.org/docs/getting-started/introduction): Create a Rails application with RES and find the next steps.
- [Installation](https://railseventstore.org/docs/getting-started/install): Add and configure RES in an existing Rails application.
- [API documentation](https://railseventstore.org/docs/getting-started/api): Generated API references for the project's gems.
- [Using Ruby Event Store without Rails](https://railseventstore.org/docs/advanced-topics/without-rails): Integrate the event store with other Ruby applications.

## Core concepts

- [Publishing events](https://railseventstore.org/docs/core-concepts/publish): Define domain events and publish them to streams.
- [Subscribing to events](https://railseventstore.org/docs/core-concepts/subscribe): Register synchronous and asynchronous event handlers.
- [Reading events](https://railseventstore.org/docs/core-concepts/read): Query events, select streams, and control ordering and batching.
- [Event sourcing](https://railseventstore.org/docs/core-concepts/event-sourcing): Model and persist event-sourced aggregates with AggregateRoot.
- [Projections](https://railseventstore.org/docs/core-concepts/projections): Derive state from a stream of events.
- [Browser](https://railseventstore.org/docs/core-concepts/browser): Inspect streams and events in a web interface for debugging and audit logs.
- [RSpec matchers](https://railseventstore.org/docs/core-concepts/rspec): Test domain events and their publication.

## Project and support

- [Source code](https://github.com/RailsEventStore/rails_event_store): Repository containing the Ruby gems and this website.
- [Releases](https://github.com/RailsEventStore/rails_event_store/releases): Release notes and version history.
- [Support](https://railseventstore.org/support): Community help, learning resources, and paid support from Arkency.
- [Contributing](https://railseventstore.org/contributing): Contribution policy and development guidance.

## Optional

- [Community](http
…

Related sites

Find similar publishers by meaning →

Other listed sites in Open source projects. See the whole category →

Machine-readable: GET /v1/resolve?q=railseventstore.org · GET /v1/domain/railseventstore.org · 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 railseventstore.org:
1. POST https://agentwebmap.com/v1/sites/railseventstore.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://railseventstore.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/railseventstore.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/railseventstore.org).
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.