01
Know what matters
Import the knowledge you already have, write together, and ask questions with citations back to the source.
- Documents and spaces
- Import and OCR
- Cited AI answers
- Comments and versions
MaWiki brings your documents, daily plan, connected tools, projects, designs, and AI assistants into one place. Capture what matters, turn it into reviewed action, and carry the same context all the way to a prototype or pull request.
Offline-friendly editing, private local AI, quick capture, MCP access, remote-device handoff, and code agents that use your own tools.
MaWiki is still a very good wiki. It is also the place where that knowledge becomes today's plan, a reviewed decision, a visual direction, and finished work.
Import the knowledge you already have, write together, and ask questions with citations back to the source.
Start with a focused Today view, capture anything in seconds, and keep tasks, calendars, and approvals together.
Turn notes and connected signals into projects, tickets, boards, requirements, and an agreed plan.
Create a design system, build a shareable prototype, generate visual assets, or send an approved ticket to a code agent.
The launch brief is waiting for review, two customer notes became suggested tasks, and product planning starts at 9.
Today brings your schedule, tasks, mentions, notes, recent work, approvals, and optional AI brief into a dashboard you can arrange around the way you work.
Connect the systems where work already happens. MaWiki keeps controlled snapshots, explains what each source can read, and sends proposed actions to a review queue before they become tasks.
Most knowledge tools make you start from a blank page. MaWiki imports the notes, exports, and folders you've already got, so the wiki is useful in the first five minutes.
No more digging through Slack threads, Drive folders, or last quarter's planning notes. Ask the question. Get the answer. See exactly which document and which paragraph it came from, so you can trust it and click through.
The wiki tells you what is true. Boards and tickets keep track of what is getting done, right next to the docs that describe it. No second tool, no copy and paste.
Feedback, bugs, and half-formed ideas land in one inbox. The AI reads them, groups what belongs together, and links each one to work you already have, so nothing slips between a good idea and who is doing it.
Develop a loose idea into requirements, tickets, a design direction, and a working visual prototype. The context stays attached when the work moves from planning into design or code.
Capture a note or use the guided idea flow. MaWiki helps turn it into editable requirements.
Set brand tokens and reusable components, generate images, then build a responsive site or app prototype.
Send a revocable preview link, collect a decision, and preserve versions of the design deliverable.
Give the approved design package or ticket to a code assistant that works on a branch for human review.
When a ticket is ready, hand it to the AI. It talks through the scope, agrees what done looks like, then writes the change on a branch and opens a pull request. You stay in control of the two moments that matter.
MaWiki can remember the preferences you choose, find relevant earlier conversations, and turn repeated instructions into skills. You can inspect, edit, undo, publish, or disable every layer.
Review what the assistant remembers, choose whether new memories need approval, undo a change, or switch memory off.
Save a good workflow once. Keep it personal, publish it to the organization, require a version, or sync it into Claude Code, Copilot, and Codex.
Set providers and models by feature, use your own key or subscription CLI, cap spend, attach images to vision models, or run locally on desktop.
It works great on its own. The moment a teammate signs up, your wiki turns into a shared brain. No replatforming, no exports, no rework.
Engineering, sales, ops, the founders' room - one workspace, separate spaces. The right docs in front of the right people.
Read, write, or admin. Per space, per person. The AI assistant only sees what each person can see, no exceptions.
Edit together with visible cursors, leave anchored comment threads, mention a teammate, and resolve the discussion without losing it.
Keep a people directory, availability, out-of-office status, delegation, mentions, and shared tasks close to the work they affect.
Review supported workspace and assistant activity in one history, inspect recent work, and manage active sessions from setup.
Invite people by email, use a replayable first-run tour, and open contextual Help on every authenticated screen when someone needs the next step.
Use hosted models for convenience, bring your own provider, connect a subscription CLI, or route selected AI features to a local model in the desktop app. MaWiki shows which model is active and lets administrators set policy and spend limits.
Open anything with Ctrl+K, switch docs with Ctrl+P, jump to a heading with Ctrl+J, ask the AI with Ctrl+Shift+A. If your hand leaves the home row, we failed.
Use MaWiki in the browser, install the PWA, or run the desktop app for local models, tray capture, code agents, and paired access to another machine.
Built by a small team in Australia. Self-funded, no investors to please. Your feedback shapes next month's release. Bug reports get answered, not closed.
Free for your first month. AUD 8 a seat after that, billed annually. No card to start.