Tetiva
Sign in
All sections

Getting started

Installation

On this page

Tetiva ships as three artifacts: a DMG for macOS, an installer for Windows and a .deb package for Ubuntu and Debian, all on the download page and free. No account is required to install or use it — the client works locally out of the box.

macOS#

Requirements: macOS 11 or newer. The build is universal — one file for Apple Silicon and Intel, roughly 32 MB.

  1. Download Tetiva-X.Y.Z-macos-universal.dmg.
  2. Open the image and drag Tetiva into Applications.
  3. Launch it from Launchpad or Spotlight.

The DMG is signed with a Developer ID certificate and notarized by Apple, so Gatekeeper opens it without a warning and without terminal workarounds. If you do get a warning, the file is most likely damaged or came from somewhere else — download it again from the download page and check Troubleshooting.

Windows#

Requirements: Windows 10 or 11. Two installers are published: x64, roughly 16 MB, and ARM64. If WebView2 is missing, the installer pulls it in.

  1. Download the installer for your architecture (x64 on most machines).
  2. Run it and step through the wizard.

The installer puts Tetiva into your user profile, %LOCALAPPDATA%\Programs\Tetiva, and needs no administrator rights. Earlier versions installed into Program Files, C:\Program Files\Saveliy Yudin\Tetiva; if such a copy is there, the installer removes it after one Windows permission prompt. Decline it and the installation still finishes, and the old copy can be removed in Settings → Apps.

The installer is not code-signed yet, so SmartScreen shows its blue "Windows protected your PC" dialog. Click More info → Run anyway. This stays true until the build gets a signing certificate; the download page says so as well.

First launch#

The first start opens a welcome screen with two options: Work locally and Connect an account. Neither choice locks you in — sync can be turned on later, and local work has no limits. A four-screen tour sits next to the choice; both the tour and the welcome screen can be reopened from settings with Show welcome.

Data goes into a single SQLite file, ~/.tetiva/data.db: collections, environments, cookies, history and settings. Point the app somewhere else with the TETIVA_DATA_DIR environment variable. Uninstalling the app leaves that directory alone.

With the app installed, go through the quick start — or, if you are coming from Postman, import your collections first.

Updates#

Starting with 1.2.1, Tetiva updates itself on macOS and Windows. At most once a day it checks for a new version, and right away if sync stops because this version is too old. When there is one, it downloads it in the background and checks the file against Tetiva's ed25519 signature and its sha256 checksum. Then a card at the bottom of the sidebar says the update is ready. Restart saves your edits, restarts Tetiva as the new version and reopens the tabs you had. Later folds the card into a line, and × hides it for that version; if you still haven't updated a week later, the card opens once more. Settings → Updates has the same Restart to update button.

The Updates section of settings has two switches for this, Check automatically and Download updates automatically, both on by default. With downloads off, the card offers Download instead. With the check off, the app makes no update requests on its own, and Check now checks on demand.

Tetiva can update itself only when it was installed the usual way: on macOS, moved out of the DMG into Applications or another folder you can write to; on Windows, with the installer. Otherwise Settings → Updates says what is wrong and links to the download page.

On Linux updates come through apt. When a new version is out, the card shows sudo apt update && sudo apt install --only-upgrade tetiva with a copy button. If Tetiva didn't come from the repository, the card shows the commands that add it, the same as in the Linux section below.

Version 1.2.0 and older only report a new version. Update them once from the download page, the same way you installed them. Updates never touch the database in ~/.tetiva, so collections and environments carry over.

Linux#

Requirements: amd64 or arm64, and a GTK3 + WebKit2GTK 4.1 stack. The package declares libgtk-3-0 and libwebkit2gtk-4.1-0 as dependencies — those are the names used by Ubuntu 22.04 and newer and Debian 12 and newer. Other distributions have not been tested.

The simplest way is the Tetiva repository: apt installs the package with its dependencies and later brings new versions with sudo apt upgrade.

wget -qO- https://apt.tetiva.app/tetiva.gpg | sudo tee /etc/apt/keyrings/tetiva.gpg >/dev/null
echo "deb [signed-by=/etc/apt/keyrings/tetiva.gpg] https://apt.tetiva.app stable main" | sudo tee /etc/apt/sources.list.d/tetiva.list
sudo apt update && sudo apt install tetiva

The repository is signed, and apt checks every package against it; the key lives in /etc/apt/keyrings/tetiva.gpg and is trusted only for this repository.

Or install a downloaded package:

  1. Download the .deb for your architecture from the download page: amd64 on most machines, arm64 on ARM.
  2. Install it with apt so the dependencies come along (the ARM file ends in linux-arm64.deb):
sudo apt install ./Tetiva-1.2.0-linux-amd64.deb

sudo dpkg -i installs the package too, but leaves the dependencies unresolved — follow it with sudo apt -f install.

The package is named tetiva. The binary lands in /usr/bin/tetiva, so tetiva starts the app from a terminal, and a Tetiva entry appears in the application menu. The database sits where it does everywhere else: ~/.tetiva/data.db.

A downloaded .deb is not verified by anyone — dpkg ignores signatures of standalone packages — and does not update itself: download the current one and install it over the old one with the same command. Installs from the repository have neither problem.

Only the .deb is published today. AppImage, rpm and an AUR package are built but not put on the site, so any third-party Linux build of Tetiva is not ours.

updated