Open Support Ticket
24/7 customer support
Open Support Ticket Chat with our AVAHOST expert
English Flag English
Login
info@ava-host.com
Sign Up Login

Shlink Hosting

Create, manage, and analyze branded short URLs through a powerful API.

Order now No setup fees
  • One click deploy
  • 1 GB RAM Memory needed
  • 15 GB Disk Space Needed
  • From 2 € Price

Official links

Shlink’s official links and original website

Related apps

See All

Tech

Docker image
shlinkio/shlink:stable
Default port
8080
Database
postgres

How Shlink works

Shlink receives an original URL through its REST API and returns a shorter path under the configured domain. Callers can request custom slugs, tags, expiration rules, visit limits, and other supported options. When someone opens the short address, Shlink records the visit and redirects the browser to the destination.

The catalogue template exposes the Shlink server rather than a bundled graphical management client. Administration therefore happens through the API or a separately selected compatible client. An API key generated with the deployment authorises management requests, while public visitors need only the final short URL.

Key Shlink features

Custom slugs and domains allow links to reflect a brand or internal naming scheme. Tags organise related links, and visit records provide timestamps, referrers, locations, devices, browsers, and operating-system information where available and permitted.

Rules can limit or expire links, and the API supports creating, listing, editing, and analysing short URLs from other applications. Webhooks and integrations can build automated link workflows around the server without requiring manual work for each address.

Shlink vs Bitly

Shlink is an API-first self-hosted URL-shortening server that gives operators control of the domain, database, and integration layer. Bitly is a commercial hosted link-management platform that packages dashboards, branded links, QR codes, campaign tools, analytics, and vendor-managed infrastructure.

Bitly may suit organisations that want a polished provider dashboard, managed account administration, and a broader commercial campaign toolkit. Shlink is more appropriate when developers need an API under their own operational control and are prepared to choose or build the management interface separately.

Who uses Shlink

Development teams connect Shlink to applications that generate share links, while marketing or communications systems use branded short domains for trackable campaigns. Internal platforms can create temporary or tagged redirects without sending link data to a third-party shortening account.

It is a poor fit for nontechnical users expecting a complete dashboard inside the catalogue deployment. Visit analytics also involve privacy and compliance considerations, so operators should decide which tracking data is appropriate for their audience and jurisdiction.

Self-hosting Shlink: requirements and cost

Resource use depends on link count, redirect traffic, visit-record retention, analytics queries, webhooks, and API activity. PostgreSQL stores short URLs, tags, configuration, and visit records. AvaHost provisions the database with Shlink, but PostgreSQL remains unmanaged.

Shlink has no separate software charge for the hosted server, and the database-adjusted recommendation is Plan 2 at €5. Shlink hosting supplies one-click server setup, a branded domain, automated HTTPS, automatic application updates, and scheduled backups. The deployment provides the API server and generated API key; a graphical Shlink client is not bundled.

F.A.Q

  • Shlink starts at €5 on Plan 2 after adding capacity for its PostgreSQL database. The Shlink package includes one-click setup, a custom domain, automated HTTPS, application updates, and scheduled backups. Redirect traffic, retained visit records, API calls, analytics queries, and webhook activity determine whether the server later needs a larger plan.

  • AvaHost provisions PostgreSQL and connects Shlink during deployment. Short URLs, tags, configuration, API data, and visit records depend on that database. PostgreSQL is included but unmanaged, so the database and any persistent application state should be treated as one service when planning updates, retention changes, exports, or recovery.

  • A custom domain can be attached to the Shlink server, with automated HTTPS applied once DNS points to AvaHost. Choose the final hostname carefully because published short URLs depend on it. Test redirects, API calls, webhooks, custom slugs, and any client configuration before distributing links broadly.

  • The catalogue deployment provides the Shlink API server and an API key, not a bundled graphical management client. Administrators must use the documented API or select a separately compatible client. This distinction matters for nontechnical teams, because creating, reviewing, and analysing links requires an interface or integration outside the server itself.