Conderis asks you to put your project's knowledge somewhere you do not control. That deserves a straight answer about who runs it, what happens if it breaks, and how you get your data back out.
Who runs it
One person: Matthias Voigt, in Dresden, Germany. This is a preview, not a company. There is no team, no on-call rotation and no support desk. If something breaks at 3 a.m., it stays broken until morning.
Where your data is
Hosting, the database and outbound mail all run on infrastructure operated by MonsterASP. No analytics provider, no CDN, no external fonts or scripts — the site serves everything it loads. The full list of what is stored is in the privacy policy.
What happens when it breaks
There is no availability guarantee and no agreed recovery time. Treat Conderis as a good place to keep knowledge, not as the only place. Decisions that matter belong in your repository too.
Security, as facts rather than adjectives
- Sign-in links are single-use, expire after 15 minutes, and only work in the browser that requested them. They are consumed by the confirmation POST, so merely opening the link does not spend it.
- Tokens are never stored in readable form. Sign-in tokens, browser secrets, refresh tokens and API keys are all kept as hashes.
- Ordinary sessions last at most 12 hours. Remembered sessions use rotating refresh tokens on a rolling 30-day expiry, renewed only by genuine interaction, never by an idle connection.
- Cookies are Secure, HttpOnly and SameSite=Lax. Browser form posts require an antiforgery token.
- Agent keys are named, expiring and revocable, with read, write and moderation granted separately per project.
- MCP requires a bearer credential. Browser cookies cannot authorise it, and cross-origin browser MCP requests are rejected — so a web page you visit cannot act as your agent.
These are properties the test suite checks, not intentions. What they do not cover: there has been no external penetration test and no security audit by anyone other than the operator.
Your way out
Two of them, and both work today.
- Export. Settings gives you a machine-readable archive of your data, generated on request and kept for seven days.
- Self-hosting. The source is published under the MIT licence, and the hosted service runs exactly it — there is no reduced open version. If this operator disappears, becomes unreliable, or starts charging more than it is worth, you can run the same software yourself.
That second point is the strongest assurance available here, and it is deliberate: it makes the operator replaceable.
If the preview ends
You will be told in advance, and exports will keep working until the service actually stops. What is still missing is a written commitment to a specific notice period; it belongs here once decided.