VolkTerm — a terminal for macOS
Many coding agents, one readable screen
A native terminal on the Ghostty engine. Workspaces, a status for every agent, sessions that come back after a reboot, and your own zsh untouched.
macOS 14 or later, Apple silicon and Intel.
An agent’s status on its row
-
Working
active
-
Waiting for you
blocked
-
Finished
completed
Products
By request
Transactional email
Emails from your code via an HTTP API: password resets, receipts, notifications. Your own domain with SPF, DKIM and DMARC, a log of every message and an explicit rejection with a reason instead of silent loss.
Request access
Learn more
By request
Short links
A short address for a post, email or QR code, with click statistics for every link.
Request access
Learn more
By request
QR codes
Static and dynamic codes with your own styling. The target of a dynamic code changes without reprinting.
Request access
Learn more
By request
Error tracker
Compatible with the Sentry SDK: change the DSN and your application’s events come here.
Request access
Learn more
By request
Tunnels
A temporary public address for a service running on your computer: show work in progress to a client or receive a webhook without a server of your own.
Request access
Learn more
By request
Monitoring
Server metrics and logs in one place, and an alert when something goes wrong.
Request access
Learn more
By request
Analytics
A visit counter for your sites with no third-party trackers or cookie banners.
Request access
Learn more
Other Volkoff products
Products of their own: they live apart from the platform’s utilities.
Coming soon
VolkoffHQ
A coordinator for an unattended agent shift: tasks and their specs, which agent holds what, token spend, and one page that shows what is in progress. One server, any number of projects.
Learn more
Coming soon
VolkVM
A native hypervisor for macOS on Apple silicon: Windows on ARM with 3D support, Linux later.
Learn more
Every accepted email is delivered or comes back with a clear rejection
We never lose email silently. A lost password reset costs more than an honest rejection with a reason, so every email has a log entry and a status.
A log of every email
You can see when an email was accepted, what happened to it next and why it did not arrive.
Rejections come with a reason
If an email is stopped before sending, the API response and the log say why.
The shared pool’s reputation is protected
Until an account is verified, email goes only to the verified addresses of the Organization’s members.
What the mail service has
- HTTP API. Email from your code in one request: password resets, receipts, notifications.
- Your own domain. The dashboard shows the SPF, DKIM and DMARC records for your domain and checks DKIM.
- Message log. Status, time and reason for every email.
- Suppression list. Addresses that must not be written to will not get an email again.
How to start
- Add a domainThe one you will send from.
- Set up DNSThe SPF, DKIM and DMARC records from the dashboard.
- Get an API keyOne key per sending domain.
- Send your first emailWith one HTTP request.
- Watch the logStatus and reason for every email.
Questions
What does “accepted” mean?
An email is accepted when the API answers with success. From then on it is either delivered or rejected with a reason, and both show up in the message log.
How do I send email?
Over the HTTP API only: from your code, with a sending-domain key.
Why can’t I email everyone right away?
Until an account is verified by hand, email goes only to the verified addresses of the Organization’s members. That way accounts created for spam cannot hurt the shared pool’s reputation.
What does “by request” mean?
A product is not open to everyone at once: an Organization sends a request, we review it and open access. If a product has not launched yet, you can join the waiting list.
What about emails that look like spam?
An email is checked before it is sent. If it is stopped, the response gives the reasons instead of staying silent.