EARLY ACCESS 0.1.1
Install SecureServe
These instructions create a local evaluation instance. Begin in a controlled environment, keep the administrator dashboard bound to loopback, and do not expose it directly to the public internet.
Download the package and SHA-256 checksum manifest. SecureServe uses TCP 2022 for SFTP, 127.0.0.1:8080 for administration, and 127.0.0.1:8443 for the user portal by default.
macOS — signed universal PKG
- Download the universal PKG for Apple silicon or Intel.
- Verify the downloaded package:
cd ~/Downloads
shasum -a 256 SecureServe-0.1.1-notarized-macos-universal.pkg
The result must match the same filename in SHA256SUMS.txt.
- Install the Apple-notarized package:
sudo installer \
-pkg ~/Downloads/SecureServe-0.1.1-notarized-macos-universal.pkg \
-target /
- Create a private working directory and copy the configuration template:
mkdir -p ~/SecureServe
cd ~/SecureServe
cp /usr/local/share/doc/secureserve/config.example.json ./config.json
chmod 700 ~/SecureServe
chmod 600 ./config.json
- Start SecureServe from that directory:
cd ~/SecureServe
/usr/local/bin/secureserve
Linux — x86-64 or ARM64
- Download the archive for your server architecture:
- Linux x86-64 for most Intel and AMD servers
- Linux ARM64 for 64-bit ARM systems
- Verify the archive. Replace the filename if you downloaded ARM64:
cd ~/Downloads
sha256sum SecureServe-0.1.1-notarized-linux-amd64.zip
- Extract it into a private directory:
mkdir -p ~/secureserve
unzip ~/Downloads/SecureServe-0.1.1-notarized-linux-amd64.zip \
-d ~/secureserve
cd ~/secureserve/SecureServe-0.1.1-notarized-linux-amd64
chmod 700 .
chmod 755 ./secureserve
cp ./config.example.json ./config.json
chmod 600 ./config.json
For ARM64, use the ARM64 archive and extracted directory names.
- Start the evaluation server:
./secureserve
The first run creates a self-signed HTTPS certificate. A browser warning is expected until you install a trusted certificate. Do not bypass certificate warnings for a public production deployment.
First-run files
SecureServe creates config.json and a local data/ directory in the working directory. The generated administrator credential is stored at data/initial-admin-password.txt with restrictive permissions and is removed after the password is changed.