myICOR vs Rahnuma.io

myICOR and Rahnuma.io are both productivity tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

myICOR

The system is a local markdown folder pre-loaded with a six-person AI team: a routing orchestrator (Larry), a research specialist (Pax), a capture agent (Penn), and others — each with a named contract and a session journal so the next model picks up where the last one left off. You bring your own LLM; the folder supplies the memory. Research produces structured notes in place, drafts inherit your established voice, and weekly review prompts surface stale items automatically. The ceiling appears when you need real-time data, API integrations, or collaborative editing — none of that is in the folder. Teams that need those reach for purpose-built tools alongside this one.

Rahnuma.io

The platform combines Kanban boards, sprint planning, AI-generated standup summaries, and deadline risk forecasting into a single cloud-hosted workspace, so you are not stitching together Jira, Notion, and a spreadsheet to see whether the sprint is healthy. The risk engine pulls from real velocity, open blockers, and capacity data to produce a scored forecast — the vendor states 80%+ accuracy on active teams. The AI assistant, powered by xAI Grok, answers plain-English questions about sprint health and generates stakeholder summaries on demand. Where the tool's ceiling appears: teams with complex cross-project dependencies or enterprise-grade audit requirements hit the edges of a platform that is still early-stage and cloud-only.

Attribute	myICOR	Rahnuma.io
Pricing	Paid	Paid
Price	—	$29/month
Free trial	No	10 days
Open source	No	No
Has API	No	No
Self-hosted option	Yes	No
Platforms	Local disk (any OS with markdown support)	Web
Pros	LLM-agnostic folder architecture, so switching from Claude to Gemini mid-project is a matter of opening the same folder in a different app — no re-pasting context, no lost session history. Persistent agent journals mean each specialist picks up from the last session, so you stop spending the first ten minutes of every AI conversation re-explaining who you are and what you're working on. Plain markdown on your local disk means zero migration risk — if the vendor disappears tomorrow, every note, contract, and workflow you built is still readable by any text editor or LLM. Larry's routing layer matches requests to the right specialist automatically, so you don't have to remember which prompt style triggers good research versus good drafting — the team handles the handoff. Open-source scaffold under CC BY-NC-SA 4.0, so you can inspect, fork, and extend the agent contracts without waiting on a vendor roadmap or paying for access to the base system.	Risk scoring breaks down into time, blocker, and capacity dimensions with specific recommended actions attached, so you know which task to unblock rather than just knowing the sprint is in trouble. The AI assistant is context-aware against your live sprint data — not a generic chatbot — which means standup summaries and stakeholder reports reflect actual task state instead of requiring manual synthesis each morning. GitHub and Bitbucket read-only sync links commits and PRs directly to tasks, so sprint progress reflects real code activity rather than whatever developers remembered to update in the board. Kanban, sprint planning, goal tracking, and risk forecasting share a single data model, which means you avoid the data drift that happens when velocity in your planning tool and blockers in your task board are maintained separately. Slack integration pushes daily digests and blocker alerts without requiring team members to open the platform, so alert fatigue stays lower and critical signals reach people in the tools they already watch.
Cons	The folder has no mechanism for live data: API calls, web scraping, calendar reads, and CRM syncs are all outside its scope. Teams that need agents to pull live information must wire up a separate integration layer and maintain it alongside the folder — which is a second system to debug. There is no multi-user collaboration model. Two people cannot edit the same folder simultaneously with conflict resolution. Teams of more than one person sharing a PKM workspace hit this wall immediately and typically move the shared layer to a tool with real-time sync — Notion, Obsidian Sync, or a shared Git repo — while keeping individual folders local. No hosted inference or built-in LLM access means every new user must already have API credentials or a local model running before the team scaffold does anything. For non-technical users who came for the AI workflows, the setup friction before first use is real and the docs leave meaningful configuration detail to the user to figure out. The agent team is fixed at the scaffold level — expanding it requires running Nolan's eight-step hiring procedure, which is a prompt-driven workflow inside the folder. Teams used to GUI-based agent builders who want to add a specialist in two clicks will find the process slower and more text-heavy than competing tools that offer visual agent creation.	The platform is cloud-only with no self-hosted or on-premise option, so teams in regulated industries where data residency or air-gapped deployment is a hard requirement cannot use it — those teams move to self-hostable alternatives like Plane or GitLab Issues. Integration scope is limited to GitHub, Bitbucket, Slack, and Google Calendar; teams using GitLab, Azure DevOps, Jira for cross-org dependencies, or enterprise SSO providers hit missing connectors and must maintain a parallel workflow or wait on the vendor roadmap. The forecasting engine's accuracy is vendor-reported at 80%+ on active teams, but that figure carries no external audit; teams evaluating it for high-stakes release decisions are making a bet on a relatively early-stage platform's risk model without third-party validation. At the point where a growing organization needs portfolio-level reporting across five or more simultaneous projects with cross-project dependencies, the single-sprint-focused interface requires manual aggregation — the kind of work the tool was supposed to eliminate.

Bottom line

myICOR and Rahnuma.io are closely matched on pricing model, openness, and API availability — pick by feature set and platform support in the table above.

Frequently asked questions

What is the difference between myICOR and Rahnuma.io?

myICOR is Paid, while Rahnuma.io is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is myICOR better than Rahnuma.io?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.