Questions,
answered.

Synapse is a multi-tenant IT documentation platform. It's where you record everything about the IT environments you manage: client organisations, their network devices, hardware and software assets, the people you deal with, important documents, and — securely — the credentials that keep it all running.

It's a modern alternative to tools like Hudu, IT Glue and IT Portal.

IT teams and managed service providers (MSPs) who need a single, secure, searchable source of truth for the environments they support. If you've ever lost time hunting for a password, a serial number, or "which switch is in the comms cabinet at site B," Synapse is built to end that.

Security is built into the foundation, not bolted on. The highlights:

• Encrypted credentials — stored secrets are encrypted at rest using AES-256-GCM, with the ciphertext padded so even a password's length can't be inferred from the database.
• Mandatory MFA — every user enrols an authenticator app; there's no opting out.
• Step-up authentication — sensitive actions (revealing a credential, approving a deletion, exporting data) require a fresh MFA challenge at the moment you do them.
• Full audit trail — every meaningful action is recorded in an append-only audit log.
• Tenant isolation — your organisation's data is strictly separated from every other organisation's.

During the current phase, all data is hosted in South Africa. Data residency is South Africa only, by design.

Synapse is a hosted (SaaS) product. Self-hosting is not offered.

No, and that is the point. South African law excludes some documents from electronic signature entirely — property sales, wills, leases of land over twenty years, bills of exchange. Others, like suretyships, need a signature no ordinary platform can issue; our courts have held electronically signed suretyships invalid.

Covenant checks every document before it can be sent. If the law excludes it, Covenant blocks it, names the statute and explains what to do instead. If it needs wet ink, Covenant produces the document, tracks it and files the signed original. There is no override, because the alternative is an agreement that is void and nobody finding out until it is tested.

No. They receive a link, read the document, and sign — nothing to install, nothing to join, no password. The invitation arrives from your own domain rather than ours, so it looks like what it is: a contract from you.

Covenant is in Alpha — deployed and running for its first organisation, by invitation. We're bringing organisations in a few at a time so we can support each one properly. Register your interest and we'll be in touch as it opens up.

You request access from the sign-in screen ("Request access"). Sign-ups are reviewed and approved by an administrator in your organisation before the account becomes active — Synapse does not allow open self-service sign-up.

New accounts require administrator approval. This is deliberate — it keeps unknown users out of an organisation's sensitive documentation. Once an admin approves you, you'll be able to sign in.

Yes. MFA is mandatory for everyone. On your first sign-in you'll be guided through enrolling an authenticator app (such as Google Authenticator, Microsoft Authenticator, or Authy) and shown a set of recovery codes. Save those codes somewhere safe — they're how you get back in if you lose your phone.

You have three fallbacks, in order:

• Recovery codes — the single-use codes you saved during enrolment. Use one at the sign-in MFA step.
• Administrator reset — an admin in your organisation can reset your MFA so you can re-enrol.
• If neither is available, contact your Synapse administrator or Forged support for identity-verified assistance.

This is exactly why saving your recovery codes at enrolment matters.

Use the "Forgot password?" link on the sign-in page. You'll receive an email with a reset link.

That's step-up authentication. Certain high-sensitivity actions — revealing a stored credential, approving a deletion or export — require you to re-confirm your identity with a fresh code, even though you're already signed in. It's an extra layer protecting the most sensitive operations.

A few things can cause this: your session reached its time limit, your password was changed (which signs out all sessions), an administrator revoked your session, or a sign-in was detected from a noticeably different device or location. If it keeps happening unexpectedly, tell your administrator.

For each client you support, you can document:

• Network devices — firewalls, switches, routers, access points, NVRs, UPSs, and more.
• Assets — servers, workstations, and other hardware and software you track.
• Credentials (the vault) — passwords and secrets, encrypted and access-controlled.
• Client users / contacts — the people at that client, and their associated accounts.
• Documents — network diagrams, contracts, runbooks (up to 50 MB each).
• Notes — free-form markdown notes.
• Tags — for organising and filtering.

Two ways: global search (full-text, ranked by relevance) and the command palette (⌘K / Ctrl+K) — a fast launcher for navigation and actions, including slash-commands.

Synapse includes an AI assistant you can drive in plain language — for example, "create client Acme Corp" or "find the firewall for site B." The AI interprets your request and always shows a confirmation before making any change. It never writes data on its own; you stay in control of every create, update, or delete.

Open the relevant credential and choose to reveal it. Revealing a secret triggers a fresh MFA challenge (step-up authentication) and shows the value for a limited time with a countdown, after which it re-hides. Reveals are rate-limited and recorded in the audit log.

Deletion is deliberate and reversible-until-final. Most things are archived first (a soft delete) rather than destroyed. Permanent deletion goes through an approval workflow that typically requires two administrators to sign off, and shows a preview of everything that would be affected. This prevents accidental or malicious loss of important documentation.

Yes — Synapse can produce an encrypted export (a ZIP) of a client's data. Exports require administrator approval (typically two admins) and are limited in frequency. The download link is signed and time-limited.

Catalogues are the standard lookup lists Synapse uses — device types, operating systems, manufacturers and models, vendors, industries, licence types, and service categories. They come pre-populated with sensible defaults, and you can add your own entries inline as you work.

Administrators manage the organisation itself: approving new users, managing all users, managing tags and catalogues, reviewing the full audit log, approving deletion and export requests, resetting a user's MFA, and adjusting organisation settings.

When someone requests access, it appears in the admin Pending Approvals area. An admin reviews and approves (or declines) it. The same principle applies to sensitive operations like permanent deletion and data export, which require administrator sign-off — often from two admins.

Every meaningful action — sign-ins, credential reveals, creates/updates/deletes, approvals, exports, and security events — is written to an append-only audit log. Admins can view and filter it, and export it to CSV. It's the security and compliance record for the organisation.

Pricing is being finalised ahead of public beta.

Synapse is currently in an Alpha production test cycle, so there's no open trial at the moment. If you'd like to join the Alpha, get in touch. Full trial availability is tied to the public-beta and billing phase, which isn't live yet.

That address doesn't correspond to an active organisation. Check the URL — each organisation has its own address. If you believe it's a mistake, contact your administrator.

If no one in the organisation can sign in, it's likely a service-side issue rather than your account. Contact your administrator or Forged support.

Search covers documented records. Very recently added items are normally available immediately, but if something's missing, confirm it was saved (not left in a draft/unsaved state) and that you have access to the client it belongs to.

Try rephrasing more specifically, including the type of thing and its name (e.g. "create client Acme Corp" rather than just "add Acme"). If the AI needs more detail, it will ask rather than guess.