Built for the ARR stack and beyond

The home for Arrsome projects,
tooling and supporting services.

Arrsome builds practical tools for self-hosted environments with a focus on release management, operational clarity, responsive maintenance and reliable project delivery. Each project lives under its own repository or subdomain while arrsome.xyz stays the clean entry point.

site featured status pull requests issues maintenance focus
Open Softarr View on GitHub Browse projects

Projects

Hosted pages and repositories with a consistent standard.

The main domain introduces the Arrsome ecosystem, points visitors to the current flagship project and gives a clear path to source code, documentation and service information. Softarr is the leading project today. Additional ARR-style tools, supporting services and documentation can sit underneath the same structure without losing clarity.

Planned
Sentinarr

A lightweight monitoring and security companion for the ARR ecosystem, designed to keep your media automation stack healthy, up to date, and safe.

GitHub organisation
Status
Service and release monitoring

Status pages publish service health, project notices and serious version-related issues that need immediate attention.

Vision

More ARR-style solutions for the parts of self-hosting that still need better tooling.

Arrsome exists to build practical software where the existing ecosystem still has gaps. That includes release oversight, verification, approvals, support services and the surrounding operational pages that help people run projects with more confidence. The goal is not to build unnecessary complexity -- the goal is to make the right tasks easier to review, maintain and trust.

We want Arrsome projects to feel well maintained, technically credible and straightforward to contribute to. That means keeping pull requests moving, responding clearly on GitHub, shipping improvements steadily and treating documentation as part of the product rather than an afterthought.

Responsive development

Pull requests and issue reports handled promptly with clear discussion, sensible review and visible follow-through where changes are accepted.

Practical scope

Projects should solve real operational problems in homelab and self-hosted environments, especially where ARR-style workflows can be improved.

Release discipline

Versioning, changelogs and upgrade paths treated as first-class concerns, not an afterthought.

Accessible quality

Interfaces that work across desktop and mobile, meet accessibility standards, and remain readable under real-world conditions.

Status

Clear status reporting when something serious happens.

A dedicated status page shows service availability, incident notes and release advisories across Arrsome projects. When a version introduces a severe regression, compatibility break or security concern, that information should be easy to find and easy to understand. The same page also publishes maintenance notices, degraded service states, known workarounds and confirmation when an affected version should no longer be used.

Alert
Serious version issues

Highlight releases that should be avoided due to instability, data risk, upgrade failures or security impact.

State
Service availability

Publish current uptime, degraded states and restoration notes for hosted pages and supporting services.

Notice
Maintenance and guidance

Share planned maintenance, rollback advice, compatibility guidance and upgrade recommendations in one place.

Languages and stack

Built with the languages and frameworks needed for modern self-hosted software.

Arrsome projects use a mix of languages depending on the problem being solved. Core services and integrations may use Python. Front-end work may use TypeScript, JavaScript, HTML and CSS. Supporting scripts, automation and deployment tasks may use Bash, YAML, JSON and Docker configuration. As the ecosystem grows, repositories may also include SQL for data work, Markdown for documentation and additional language choices where they fit the product.

Code
Primary languages

Python, TypeScript, JavaScript, HTML, CSS and SQL.

Ops
Operational formats

Bash, YAML, JSON, Docker and Markdown.

Standards
Quality expectations

Readable interfaces, maintainable code, consistent documentation and accessible presentation across desktop and mobile layouts.