Weft Start free trial

FAQ

Frequently asked questions

What hardware does a site need?

Any machine that runs Ubuntu 24.04 or 26.04 LTS on x86-64 or ARM64 — a small PC, a server, or a cloud instance — with one or two internet connections. A site can also run as a Docker or Proxmox container (as the console sets one up, a container site has a single network port, so it links to your other sites but can't carry an office's own network), or be launched into your own AWS or Azure account from the console. You bring the hardware; there is no appliance to buy or ship.

Does my traffic pass through Weft's servers?

No. Traffic goes directly between your own sites over WireGuard, or through a hub that is also one of your sites. The Weft control plane handles configuration and health, and is never in the path of your packets.

What happens if the Weft control plane is unreachable?

Your network keeps forwarding. Every site holds a complete copy of its configuration and keeps applying it. You cannot make changes until the control plane is back, and nothing that is already working stops. The one thing that waits for it is a hub failover: if your active hub also fails meanwhile, the standby takes over once the control plane returns.

Which devices can connect as roaming clients?

macOS and Windows. Each device generates its own WireGuard key and joins with a one-time invitation, so its private key never leaves it. You choose per client whether it sends only company traffic through Weft or everything.

Will it work with the routers and firewalls we already have?

Yes. A site can exchange routes with your existing equipment over OSPF or eBGP, hand off a routed network on a dedicated port, or stretch a layer-2 segment. Internet traffic can leave through your own perimeter firewall rather than from each branch.

How is Weft priced?

Per site and per roaming client, monthly, with every feature on one plan. See pricing.

How does the free trial work?

Thirty days, up to three sites and ten roaming clients, every feature, and no card. If you need longer, ask and we will extend it once.

What happens when a trial ends or a payment fails?

Your network does not go down. After a 14-day grace period the console becomes read-only — no changes or new devices, though you can always quarantine or remove a device or site — while every site keeps forwarding on its last configuration. We will never switch off a running network to collect a bill.

Where is our data held?

The control plane and its data are in AWS's London region (eu-west-2). It holds your network's configuration, health measurements and device public keys, and records of connections: what your policy refused, which devices used each application, and, if you turn it on, every connection your sites allowed (who, to which address and port, and when). It never sees what is inside your traffic, or any WireGuard private key. The one exception to London is Ask Weft, the console's assistant: if someone uses it, their question and the network data needed to answer it are sent to Anthropic, outside the UK, which normally deletes them within 30 days. The privacy notice has the detail.

What encryption does Weft use?

WireGuard, for every tunnel: Curve25519 for key exchange and ChaCha20-Poly1305 for each packet, with keys renewed every two minutes. WireGuard has one fixed set of algorithms, so there is nothing to negotiate or misconfigure. ChaCha20-Poly1305 is not FIPS-approved, so Weft is not FIPS 140 validated. More on the security page.

Can we sign in with our own identity provider?

Yes. An administrator connects Microsoft Entra ID, or any other OpenID Connect provider, from the Settings page, tests it with a real sign-in, and gives each of its groups a console role. The Entra guide walks through it. Without one, people sign in with Google, or with an email address and password, with an optional authenticator app.

Something not answered here? Email hello@weftnetworks.com. Found a problem, or want a feature? support@weftnetworks.com.