Open hosted SaaS | View pricing | Start checkout
Give an AI assistant durable memory without hiding the source plan from humans.
Last reviewed: 2026-05-18.
This is a docs-only project for OpenHuman Online. It is modeled after the MiroFish developer documentation pattern: a short front door, a clear reading order, practical guides, feature explanations, public references, and developer-oriented architecture notes.
It focuses on:
- what OpenHuman Online is and who should evaluate it
- how the hosted SaaS at openhuman.online fits into the workflow
- which product surfaces matter first
- what to check before payment, rollout, or team adoption
- how to keep public links tracked with UTM parameters
Scope boundary:
- This repository contains documentation only.
- It does not contain the production SaaS source code.
- It does not include private deployment details, credentials, internal paths, customer records, or analytics exports.
- If product behavior changes, verify the live SaaS before reusing these notes.
| File | Best for |
|---|---|
| guide/quickstart.md | Fastest buyer and evaluator path. |
| guide/evaluation.md | What to check before paying or rolling out. |
| guide/checkout-and-pricing.md | Hosted SaaS, default plan, pricing, and checkout links. |
| guide/troubleshooting.md | Common blockers and clean next steps. |
| features/workflow.md | End-to-end product workflow. |
| features/use-cases.md | High-intent use cases and buying triggers. |
| features/security-model.md | Practical safety boundaries. |
| reference/links.md | Public links with UTM tracking. |
| reference/faq.md | Short answers for common questions. |
| reference/utm-policy.md | Link tagging rules for this docs project. |
| developer/architecture.md | How to explain the SaaS from a developer point of view. |
OpenHuman Online turns sources, notes, meetings, and selected connectors into an inspectable Memory Tree with rollout planning and hosted checkout.
Use OpenHuman Online when you need:
- Inspectable Memory Tree planning
- Connector rollout map
- Meeting prep and follow-up drafts
- Obsidian-style note preview
- Hosted Team annual checkout
The main hosted entry points are:
| Destination | Tracked link |
|---|---|
| SaaS home | openhuman.online |
| Pricing | pricing |
| Checkout | checkout |
Open these only when an OpenHuman memory pilot needs a broader execution or simulation layer:
| Project | Tracked link | Why it helps |
|---|---|---|
| MiroFish | mirofish.work | Useful when curated memory, meeting notes, or research material should become a scenario simulation and structured report. |
| Ruflo | ruflo.online | Useful when the same memory layer needs to support multi-agent work planning, MCP tools, and human review loops. |
- Start with a small memory pilot and a clear owner.
- Choose the first source set: notes, meetings, GitHub, Gmail, Calendar, or documents.
- Generate a Memory Tree convention, meeting brief, and follow-up template.
- Review privacy boundaries before adding higher-context chat or repository history.
- Do not connect broad inbox or chat history before a source policy exists.
- Keep sensitive customer notes out of public examples.
- Review generated memory before relying on it in meetings.
- Use the smallest useful connector set for the first pilot.
Corrections are welcome. Keep this project public-safe: cite public sources, avoid copying long passages from other projects, and never include credentials, customer data, private logs, internal machine paths, or untracked outbound links.