Kutt Hosting

Shorten links on your own domain and see click statistics for each one.

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

Tech

Docker image
kutt/kutt:latest
Default port
3000
Database
postgres

How Kutt works

Kutt converts a long destination into a shorter address that can use a generated or chosen alias. Link owners can edit or remove their redirects, apply expiration rules or passwords, and review private statistics. Custom domains let an organisation present links under its own brand rather than a shared public shortener.

The REST API and administration pages support programmatic creation and user oversight. In the catalogue configuration, anonymous links and registration are disabled, Redis is enabled for caching, and mail is switched off. Kutt has no automatic first-run account, so the owner temporarily enables registration, creates the account, and disables registration again.

Key Kutt features

The default restrictions reduce the chance that an exposed shortener becomes an open redirect service for strangers. Custom aliases make campaign or documentation links readable, while expiry and password options add control for temporary or limited-access destinations. Private statistics provide basic visibility into link use.

The current upstream project warns that the former kutt.it domain is no longer controlled by its maintainers and may imitate Kutt. The hosted page therefore uses the current official kutt.to identity and the self-hosted domain selected by the customer. Application email is disabled, so password reset mail is unavailable.

Kutt vs Bitly

Kutt is a self-hosted shortener with custom domains, editable links, private statistics, user controls, and an API. Bitly is a provider-managed platform for short links, branded domains, QR codes, analytics, campaign workflows, and commercial administration across its subscription plans.

Bitly may suit organisations that want a maintained service, integrated QR tooling, and provider-operated analytics without managing a database or cache. Kutt is better suited to operators who want control of the shortener and can enforce registration policy, monitor abuse, protect the domain, and maintain the application stack.

Who uses Kutt

Marketing and communications teams use Kutt for memorable campaign or event links under a company domain. Documentation teams shorten long knowledge-base addresses, while internal IT groups create controlled redirects for service portals, onboarding resources, or temporary migration notices.

A shortener can be abused for phishing, malware, or concealment if link creation is exposed carelessly. Owners should keep registration closed, review created links, protect the administrator account, and remove suspicious redirects promptly. The public hostname should also be monitored for reputation problems caused by misuse.

Self-hosting Kutt: requirements and cost

Kutt load depends on stored links, redirect traffic, statistics collection, API calls, active users, custom domains, and administration sessions. PostgreSQL stores links, aliases, users, domains, settings, statistics, expiration rules, and access controls. Kutt database memory sits outside the exported application minimum, which triggers the confirmed step-up.

AvaHost maps Kutt to Plan 2 at €5. The one-click Kutt stack includes PostgreSQL, which remains unmanaged by AvaHost. Kutt includes automated HTTPS for a custom domain, application updates, and scheduled backups. Redis is packaged for caching, registration and anonymous links start disabled, and application email is unavailable. Create the first account by temporarily enabling registration, then close it again; password resets cannot be sent by email.

F.A.Q

  • Kutt starts at €5 on Plan 2 after allowing for its PostgreSQL container. Stored links, redirect volume, statistics, API calls, users, and custom domains drive resource use. Keep registration and anonymous creation disabled unless there is a specific controlled need, because an open shortener can attract abuse and reputation problems.

  • The stack provisions PostgreSQL for links, users, domains, rules, statistics, and settings, plus Redis for caching. Kutt receives PostgreSQL with the deployment, while its records remain operator-managed. Both services, the application secret, and the Kutt configuration belong to one deployment, so updates or recovery should preserve the complete stack rather than only the web container.

  • Kutt supports a custom domain, and AvaHost applies automated HTTPS after DNS points to the hosted application. Use your selected hostname rather than the retired `kutt.it` domain, which upstream states is no longer under project control. Test redirects, custom aliases, statistics, API calls, and password-protected links after attaching the domain.

  • The catalogue starts with registration and anonymous links disabled. Temporarily change `DISALLOW_REGISTRATION` to false, register the intended owner, then return the setting to true. Application email is disabled, so password reset messages are unavailable. Store the owner credential separately and avoid reopening public registration unless access is carefully supervised.