RiftRift

Documentation

Quick Start

The fastest way to get Rift working is through the CLI. It walks you from account creation to branded domains, health checks, and your first real link.

What You End Up With

One branded link, routed everywhere

One public URL for people to click, with Rift routing each tap to the right destination.

click trackedattribution readyagent-readable

Recommended

Use the CLI

This is the best path if you want the smoothest setup. Rift guides you through signup, custom domains, diagnostics, and first success without making you remember the whole API.

curl -fsSL https://raw.githubusercontent.com/saltyskip/rift/main/client/cli/install.sh | sh

Or install from source: cargo install --git https://github.com/saltyskip/rift.git rift-cli

Advanced

Doing this manually?

If you prefer raw API calls and manual DNS setup, use the manual setup guide. That path is better for operators who want to script everything or understand every infrastructure step.

CLI flow

1

Create your account and local config

Start with rift init. It verifies your email, saves your secret key locally, and helps you create a first starter link.

rift init
2

Set up your branded domain

Rift guides you through your primary branded domain, verifies DNS, and can continue straight into your alternate domain for stronger Open in App behavior.

rift domains setup

If you want the DNS details behind this step, read Custom Domains.

3

Check what is ready

Once the domain flow is done, rift doctor tells you what you can already do and what is still worth finishing before production.

rift doctor
4

Create and inspect links

After onboarding, create a real link and test how it resolves across web, iOS, and Android.

rift links create
rift links test LINK_ID

Next steps

You now have a working setup on Rift's shared domain. Pick your next goal — most developers start with custom domains or an SDK integration.