Frequently asked questions

If you run more than one project or client, the domains, SSL, hosting and subscription renewals, uptime status, production errors, credentials, expenses and client emails scatter fast. It gathers all of it into one panel per project and warns you before anything expires, breaks or goes down.

Its centre of gravity is operations: what renews when, what's up, what's throwing errors, where the secrets live and where the money goes. The work that falls out of that layer does get a board per project — owner, priority, due date — but the aim isn't to replace the tool you run sprints in; it's to make visible the work that tool never sees.

Freelance developers and designers, digital agencies, software teams running their own product, and founders juggling several side projects. The common thread: being responsible for more than one live system at once.

Less than a minute. You create your workspace, add your first project and a few renewal dates; reminders and monitors start working from that moment. No migration, no setup wizard.

No. Vault entries are encrypted and decrypted in your browser with AES-256-GCM; only ciphertext reaches the server. It's a deliberate architectural choice: data we can't access is data we can't lose, sell or leak. Your vault passphrase never reaches us either.

You regain access with the recovery code issued at setup. But if you lose both your passphrase and your recovery code, the nature of zero-knowledge means the vault contents are technically unrecoverable — there is deliberately no back door to make up for it.

You do. Your content is yours; export it anytime, and delete it permanently when you close your account. None of it is processed for advertising or profiling, or sold to third parties. We use no third-party advertising or tracking cookies.

All transfers are encrypted with TLS, vault contents and notification-channel configurations are stored with AES-256-GCM, sessions are validated server-side, and every critical action is written to an immutable audit trail. Passwords are irreversibly hashed; plaintext is kept nowhere.

No, because the fingerprint doesn't replace the passphrase. Your identity's private key already exists in two sealed copies — one under your passphrase, one under your recovery code; biometrics add a third. The key is derived from the device's own sensor via the WebAuthn PRF extension; what sits on the server is an opaque blob and a salt. A full database dump is useless without the finger. And losing the device is never a lockout, because your passphrase and recovery code are exactly where they were.

Sharing works by reference: the link carries which item to open, never the secret. Reading it still requires a session, membership of the project, a vault grant and the recipient's own passphrase. So a leaked reference is the address of a locked door — which is precisely what makes it safe to paste into a chat where a password never was.

Domains, SSL certificates, hosting, software subscriptions, licenses — anything with a date and an amount. Each record keeps its type, term and cost; reminders land in your email and connected team channels before the deadline.

Your monitors are polled with an HTTP request every minute, response time recorded. When a check fails, the monitor confirms the state, notifies your team by email and connected channels, and sends a resolution notice when the service recovers.

You can give each project a public status page showing its monitors live. Publish it on your own domain, under your own brand if you like — so during an incident your clients check the page instead of flooding your inbox.

You give each project its own email address. Client messages sent there — attachments and all — collect under the relevant project instead of personal inboxes, and replies go from the same thread. Communication lives with the project it belongs to.

Yes. Log each expense in its own currency and see monthly and yearly totals per project. Understand at a glance what a project actually costs and where your margin sits.

No. We speak the Sentry ingest protocol — Laravel, NestJS, Django, Rails, Go, .NET: whichever official Sentry SDK you already use works unchanged, you just point the DSN at your project. Cron jobs, shell scripts and automation flows with no SDK can POST plain JSON instead. There is no separate library of ours to learn or keep up to date.

It is scrubbed on arrival. Request headers, cookies and token-shaped fields are stripped before anything is written, so the stored event never held them. Errors are then grouped by fingerprint, which is what keeps one fault firing ten thousand times from being ten thousand rows — and what makes a sudden spike visible.

They turn the processes you repeat on every project — domain setup, going live, wiring analytics, legal compliance — into ready-made playbooks you apply to a project in one click. Add a step to the template later and it lands on every project already using it, so the process lives in the system rather than in one person's memory.

It recognizes which project the open tab belongs to and brings that project's credentials, TOTP codes and operational context to it, with the vault unlocked by Touch ID or Windows Hello. You can also create renewal, expense and task records from the page where it happened — which is exactly where a record otherwise disappears into "I'll enter it later".

No. Owners and admins see the whole workspace; members only see the projects assigned to them. Vault access is per-project too — a member can only reach the secrets of the projects they're assigned.

It depends on your plan: Studio covers 10, Agency 50, Armada unlimited team members. Invite links work as long as your plan is active; members create their own account and join the workspace.

Yes. Every critical action — adding a renewal, changing a monitor, assigning a member, vault operations — is written to the audit trail with who and when. The trail can be filtered and reviewed after the fact.

Yes. The Solo plan is free forever: 1 project, the renewal radar, uptime checks every 5 minutes and the zero-knowledge vault. No credit card required; no trial that expires out from under you.

Every new workspace gets Studio features free for 14 days. If you don't decide by the end, you simply drop to the free Solo plan — no surprise charge.

Yes, in one click. No commitment; cancellation takes effect at the end of the current billing period and your access runs until then. You can export your data on the way out.

Upgrades take effect immediately; you get the new project and member limits right away. On a downgrade you're asked to fit within the new plan's limits, and the change applies from the next period.