Self-Hosting

The public @hasna/skills package includes skills-serve, a self-hosted HTTP server, plus its CLI, MCP server and SDK. Run it for your own catalog and execution infrastructure, with a separate API URL and credential profile.

Skills.md is the separately operated commercial service. Its hosted accounts, credits, payment processing and managed execution are implemented in the private product. Installing the public server does not install those commercial services.

Start the public server

Install @hasna/skills and inspect its server help:

Install

bun install -g @hasna/skills

Server help

skills-serve --help

For a local server, bind to loopback:

Start locally

HOST=127.0.0.1 skills-serve

The default server uses a persistent SQLite database in the Skills data directory and listens on port 8787. HASNA_SKILLS_DATABASE_URL selects a SQLite file or PostgreSQL connection. PostgreSQL deployments require the public skills-migrate command before serving. Database credentials belong only on the server.

Before making the server reachable by others, follow the public package's server documentation for authentication, durable storage, worker execution and deployment configuration. Configure credentials through your secret store; do not paste them into logs or source control.

Select your instance

Use a profile distinct from the commercial skills-md profile:

Select your server

skills --profile internal setup --api-url https://your-server.example/api/v1 --json

Authenticate with the method supported by that server, then inspect its capabilities. Email signup, checkout and billing may be unsupported on a self-hosted instance.

Supported features

skills --profile internal capabilities --json

For MCP, set HASNA_PROFILE=internal and HASNA_SKILLS_API_URL=https://your-server.example in that host's server environment. CLI, MCP and SDK use the selected API and its credentials. Changing the internal profile does not repoint Skills.md or another Hasna application.

The same released client can connect to both instances. Accounts, data, credit balances and enabled capabilities belong to the selected server; they are not automatically shared.

Support

For a guided rollout or dedicated managed deployment, contact support@hasna.com.