Rethinking Jira & Confluence: Deploy Your Own Customizable Issue & Wiki Stack in Just 15 Minutes

'Rizm' delivers Jira’s core benefits in a stable, lightweight stack without the risk of EOL or sudden interface changes

Cloud-based project management tools are convenient. However, as they become more feature-rich, they often become heavier and their UI changes frequently. This can create frustration.

In addition, there has been recent news that Jira Data Center will reach end of support in 2029. As a result, the available options for on-premise environments are becoming more limited.

In this situation, we are building Rizm, focusing on fast performance and full control by the team itself.

https://www.youtube.com/watch?v=oibzDh0yWN4

1. A Structure You Can Keep Using Without External Dependency

Rizm is designed with the intention of “running stably for a long time.”
It avoids dependence on specific platforms or external services. This minimizes the impact of feature changes or service termination (EOL) decided by vendors.

• Backend: Rust (independent binary, runs without relying on external services)
• Frontend: React + TypeScript
• Runtime: Docker

2. Customization by “Rebuilding the Core”

Until now, it has been common to operate tools by filling missing features with add-ons. However, in cloud tools where the source code is not available, learning restrictive APIs and add-on specifications becomes a bottleneck.
With Rizm, the frontend will be open source (planned), allowing you to directly modify the UI structure and screen behavior.

Instead of “consuming a finished product,” you reshape the tool to fit your needs. It is a self-hosted, self-built style.

Rizm intentionally keeps its features and structure simple. With agentic coding, directly adjusting the core system to optimize it for your team becomes realistic.

Instead of learning the specifications of a black-box tool, you redesign the tool yourself. This freedom is one of the reasons to choose self-hosting.

3. The Trade-Off of Self-Hosting

In the past, configuration and operational effort were major barriers to self-hosting. Today, by using LLMs, it has become much easier to apply widely known best practices. The hurdle for setup and maintenance has dramatically decreased.

In exchange for taking responsibility for management within the team, you maintain an environment that continues to run at a speed you are satisfied with.

We believe this is a reasonable choice for modern team operations and project management that prioritize efficiency and freedom.

Deploy in 15 Minutes — Supports Win11, Linux, macOS

Rizm is currently in beta(free). Because it runs with Docker, you can set it up on Windows 11, Linux, or macOS with just a few commands in about 15 minutes.

• Distribution site: https://github.com/test-perspective/rizm-beta
• Overview page: https://rizm.test-perspective.com/

Finally

Why not step away from external factors such as specification changes and EOL, and grow a tool that truly fits your hands — by your own hands?

What features do you prioritize in a self-hosted PM tool? I'd love to hear your feedback!

Comments

[ken_test-perspective]

beta7 released!

Improvements

• Enhanced user management and post-creation behavior.
• Improved branch and pull request workflow feedback.
• UI improvements across task, board, and issue detail views.
• Improved field editing experience, including date handling and layout flexibility.
• Minor usability improvements around SCM operations.

MCP / AIT

• Improved MCP API key setup experience.
• Enhanced AIT instruction capabilities.
• Known limitation: Manifest history cannot revert to the initial version.