reen.tech

What It Is

REEN is a Research & Engineering Platform from Rhoe, LLC-FZ, built for scientific research and engineering development workflows. The platform consists of three parts: Radar, Library, and Engineering. Radar focuses on scientific paper feeds; Library is for document analysis and AI-generated knowledge graphs; Engineering covers Gantt planning, AI Conference, Ex-Help, Artifacts, and Strategic Plans.

Core Capabilities

From a developer-tooling perspective, REEN’s key focus is making engineering plans accessible to APIs and AI Agents. It provides a REST API, an OpenAPI specification, LLM-readable documentation, and a native MCP Server. The MCP Server can be used by Claude Code, Cursor, Codex CLI, and other MCP-compatible Agents. Its tools cover plans, tasks, progress, narrative documents, Ex-Help, Artifacts, strategic canvases, Research Library, and Conferences. The API uses backend.reen.tech, supports Bearer Token/JWT authentication, and has a rate limit of 60 requests per token per minute.

Pricing and Deployment

The main documentation does not disclose pricing, plans, free quotas, or payment methods, so its value for money can only be assessed conservatively. It is also unclear whether the overall platform is open source; only the MCP Server provides GitHub clone and npm build instructions. No complete self-hosting guide was found, and the current API points to the official backend.

Pros and Cons

A major strength is that the documentation is quite engineering-oriented: it includes versions, update times, endpoints, request/response examples, curl examples, authentication and rate-limit details, and a reminder that API calls should not be sent to the frontend domain. The feature mix is also distinctive: Gantt execution, audit logs, SSE, WebSocket, multi-model conferences, and knowledge graphs can form a closed loop for R&D work. The downsides are the lack of commercial information, the higher configuration barrier because the Research workflow requires local AI submission for analysis after segments_ready, and the 60 rpm rate limit, which may be somewhat tight for high-frequency automation.

Who It’s For and Access from China

REEN is better suited to researchers, R&D leads, and engineering teams already using Agents such as Claude Code, Cursor, and Codex CLI. It can be used for planning breakdowns, progress tracking, AI-assisted discussions, and structuring document knowledge. Information on access from mainland China, payment, and compliance is not disclosed, so these remain unknown. If access is unstable, alternatives such as Jira, Linear, Notion AI, Zotero, Elicit, and Dify may be worth considering depending on the use case.