Multiple customers. At the same time.
This was my number one problem.
I may need to access a server at one customer while working on the network of
another — without losing access to my own local network.
On Mac, Paart can run multiple WireGuard connections simultaneously. Each tunnel
keeps its own routes: I stay connected to my own environment while accessing the remote
networks I need.
No more disconnecting from one customer just to connect to another. How this works, and what it rests on.
That is how macOS behaves today rather than something Apple guarantees: nothing in the
API commits to it, and a later version of the system could change it. On iPhone and
iPad, one connection is active at a time.
The right DNS for the right network.
Accessing server.customer.local over HTTPS sounds
simple.
But if that name only exists on the customer’s DNS, using their DNS for the
entire machine can break name resolution on my own network. And once several customer
networks are connected at the same time, that approach simply does not scale.
That is why I implemented split DNS in Paart. Customer domains can be resolved
using the customer’s DNS while everything else continues to use my normal DNS.
I can access internal resources using their proper hostnames and HTTPS
certificates, without giving up access to my own network. How split DNS works.
My connections. On all my devices.
When I add a new WireGuard configuration on my Mac, I do not want to recreate it
or move it by hand to my iPhone and iPad.
Paart synchronises connections natively through iCloud. Add a connection once,
press “Synchronise Now”, and find it on your other devices.
Other destinations are under consideration for people who are not entirely
inside the Apple ecosystem — WebDAV, Google Drive, OneDrive, SFTP and Dropbox. The goal
remains the same: you choose where your data is synchronised.
See the roadmap.
On the free tier, sync runs while you have a single connection. It stops as soon as you
import a second, and can run again once you are back to one. Paart Pro syncs all of
them. Sync never runs in the background: it runs when you press “Synchronise Now”.
Forty customers. A lot of configurations.
Before I give a WireGuard configuration to a customer, I need to test it myself.
And afterwards, I need to keep it — because when that customer needs it again six
months later, I want to find it immediately.
With a handful of connections, that is easy. With dozens of customers and
multiple devices per customer, it is not.
Paart lets me organise connections into folders, sort them and filter them, to
find exactly what I am looking for. When I need to send a configuration, I can share it
as text together with its QR code.
What used to become a collection of configuration files is now an organised
library.
Connected does not always mean reachable.
A WireGuard tunnel can be connected while the server I actually need is
unreachable. That is not very useful.
For every connection, Paart lets me define the resources that matter. I can add
an IP address and, when needed, a specific port, and give each resource a useful name:
firewall, NAS, RDS, PBX, server.
As soon as the VPN connects, Paart checks those resources and shows their status
directly on the connection card — reachable, or unreachable.
One glance tells me whether the network I actually need is working.
When something breaks, I want to know why.
Logs are essential when a tunnel does not behave as expected. But with many
connections, a wall of raw WireGuard logs is not always what I need.
Paart lets me filter logs by connection, show only errors, and export or share
them easily.
Less noise. Faster troubleshooting.
Change DNS without editing configurations.
At the office, at home, at a customer site or while travelling, the DNS server I
want to use can change. I did not want to edit WireGuard configurations every time that
happened.
So Paart lets me define the DNS servers I use in Settings, and switch between them
from a dropdown. No configuration editing required.
Paart
