ShnDock中文

Docs

Documentation

Unified documentation for the website, downloads, updates, privacy, terms, and disclaimers.

Updated2026-05-31English site
Website access

The website publishes product information, download entry points, release records, Release JSON, platform status JSON, and legal documents.

It does not receive desktop API keys, providers, prompts, Agent Skills, benchmark history, or local logs.
Desktop application

API tests, API cards, providers, prompts, Agent Skills, and reports are processed on the user's device.

ShnDock does not provide API key cloud sync, a web console, or hosted storage for third-party account credentials.
Third-party interfaces

When a user runs an API test, the request is sent to the provider, relay, local model service, or custom endpoint selected by the user.

ShnDock does not control third-party logging, billing, availability, service terms, or data-processing practices.

Overview

ShnDock is a local-first desktop application for OpenAI-compatible API testing, API cards, provider presets, benchmark prompts, user prompts, and Agent Skill documentation.

The official website is used for product information, download entry points, release records, update manifests, platform status, and legal documents. It does not provide a web console, online API testing, desktop API key collection, or API key cloud sync.

Website and downloads

This documentation covers shndock.com, official download files, public Release JSON, public platform status JSON, and the basic local-data boundaries of the ShnDock desktop application.

The website is deployed on Vercel and may use Vercel Web Analytics to understand anonymous visit trends, traffic sources, and basic device information. This information is used to improve the website and download experience, not to build desktop user profiles.

Public static resources include /releases/latest.json, /releases/history.json,/stats/platform.json, and installer files. Accessing the download page does not require an account and does not collect local desktop configuration.

Local data

API keys

API keys remain on the user's device by default and are stored through Electron safeStorage using system-level local encryption.

They are not uploaded to the official website and are not written into benchmark history, logs, Skill Packs, or the browser extension.
API test records

ShnDock records TTFT, total latency, output speed, failure classification, request diagnostics, and token-usage source.

Plaintext API keys are not written into test records. Test results are for diagnosis and comparison, not billing.
Provider / Prompt / Skill

These assets are created, edited, imported, exported, or deleted by the user in the desktop application.

They are not stored by the website and are not automatically published to any public platform.
Export files

.sapi re-encrypts API card data with a user-provided password; .shndock-backup is used for encrypted full workspace backups.

Users are responsible for storing export files and passwords. Recovery cannot be guaranteed if the password is lost.

API key boundaries

API keys remain on the user device by default. ShnDock uses Electron safeStorage to store keys through system-level local encryption. If system encryption is unavailable, the desktop application should not degrade to weak pseudo-encryption such as base64 for newly saved API keys.

When a saved card is used for testing, the renderer passes only the cardId. The main process decrypts the key and sends the request. API keys are not uploaded to the ShnDock website, written into test history, logs, reports, Skill Packs, or the browser extension, and are not synchronized through the website to any third-party platform.

Third-party interfaces

When users run API tests, requests are sent to the official endpoint, relay, local model service, or custom provider configured by the user. Those third parties may process request content, logs, account data, rate limits, billing, and compliance obligations under their own rules.

Users are responsible for confirming that they are authorized to use the relevant API keys and endpoints. ShnDock does not control third-party availability, response quality, pricing, retention policies, or terms of service.

Exports and backups

.sapi files are used for cross-device API card migration and are re-encrypted with a user-provided password at export. .shndock-backup is used for encrypted full workspace backups.

Users are responsible for storing export files and passwords. Weak passwords, disclosed passwords, compromised devices, or leaked backup files may expand user risk exposure.

Update checks

The ShnDock desktop application checks for updates by reading https://shndock.com/releases/latest.json. The first update-check implementation does not require an account and does not upload API keys, providers, prompts, Agent Skills, benchmark history, logs, local paths, or device identifiers.

Windows 1.0.0 is currently available. macOS and Linux are not yet open. The current Windows installer is unsigned; file integrity is defined by the file size and SHA256 published on the download page and in the release JSON.

Browser extension Beta

The browser extension is a beta companion feature for reading public card metadata through local loopback. It does not read API keys stored by the desktop application and should not receive plaintext keys from the desktop application.

Deletion and uninstall

Users can delete API cards, providers, prompts, Skills, and API test records inside the desktop application. Uninstalling the application does not necessarily delete all local data or user-created export files.

Local user data is typically stored under C:\Users\<User>\AppData\Roaming\shndock\. Users are responsible for managing exported .sapi files, .shndock-backup files, downloaded installers, and other local backups.

Public contact channels