Apogee FAQ

As soon as it's ready! I'm personally using an internal alpha version now, and I'm aiming for an initial release in Autumn 2025.

Apogee's Desktop component will only support macOS initially. Support for Linux is planned; support for Windows is not currently planned.

Apogee's Server component will run on any reasonably modern Linux system. A Debian repository will be available, and RPMs will be downloadable. ARM and x86 devices will be supported.

You'll need to:

• Install Apogee on your desktop and servers
• Add a line to your desktop's SSH config
• Configure Apogee on your desktop to work with your favorite tools (but note, it'll come with Sublime Text and VS Code support out of the box!)
• Optionally, set up aliases like subl or code in your servers' shells

Apogee 1.0 is designed to work well with text files, or directory trees containing primarily text files, like a Wordpress theme, an Nginx configuration, or a Docker Compose file.

It won't work well on a directory tree of really big files, like photographs or videos.

Don't plan on using Apogee to edit photos or videos, and don't plan to open the entire /home or /srv directory tree at once. Use it to open a targeted set of files or directories depending on the task at hand.

I'm planning to launch Apogee as a subscription with per-user licensing.

Personal/homelab licenses will be inexpensive and come with limited support.

Business licenses will come with more extensive support or troubleshooting, and a money-back guarantee if Apogee doesn't work in your business's environment.

Yes, Apogee is secure. It builds atop SSH and can't circumvent Linux file permissions. Using Apogee only gets you access to things you can already access, on machines you can SSH into; and installing Apogee doesn't grant anyone new access to your machine.

Apogee doesn't rely on any outside servers, third-party or otherwise — it's just your desktop and your server.