goto · by DopeCode
Short links on your own domain, and every click counted
Your organisation gets go.yourcompany.com: links you choose, sent on from memory in well under a millisecond, and the clicks behind each, counted on a server you pick. Nobody's address is kept.
What it does
A short link that knows where to send each visitor, and says what happened after
Every click counted, and nobody followed
Referrers, countries, devices, systems, browsers, languages, destinations and scans, for any period against the one before. Each narrows the rest: the iPhones from LinkedIn in Germany, last week.
A visitor is counted once a day and never followed to the next. Crawlers and chat previews are kept apart, and not counted unless you ask.
One link, the right door for each visitor
iPhones to the App Store and Android phones to Google Play; a country to its own page; a share of the rest to a second page, each visitor on the same side all day.
A link can wait for its start, end on a date or after a number of clicks, ask for a password, or open once: the first person through ends it, and a chat drawing its card never uses it up.
Made to be handed out
A QR code in your colours, as SVG or PNG, that counts its scans apart from clicks. The title, text and image a chat draws for the link. And + after any short link, to see where it leads before going there.
Every destination is checked every few hours: one that stops answering is marked broken, one that moved for good, moved.
Slugs you choose
go.yourcompany.com/docs, or six letters and digits nobody can misread. Matched without case.
Destinations checked
Every few hours. One that stops answering is marked broken; one that moved for good, moved.
An API and CSV
What the pages do, as JSON with a key. Links in and out, clicks out, as CSV.
⌘K and the keyboard
Find any link or page from anywhere, make one with n, copy the short link with c.
Your team, and no one else
An owner adds the people who may make links. There is no sign-up page to find.
Backups of its own
The server copies its own database every day, so nothing else has to open it.
Where it runs
Its own server process and its own database, for one organisation
No goto shares a database with another. Pick where yours runs; everything else is the same. DopeCode's own runs at go.dopecode.com.
On a DopeCode server
Priced per organisation
- On a server of ours in the EU
- Its own process, database and system user
- Certificate, updates and daily backups: ours
- The country database kept current
On your own server
Priced per organisation
- Installed on a Linux server of yours, over SSH
- The database never leaves it
- x86_64 or arm64, with systemd, nginx and certbot
- Each release from us; one that fails its health check is rolled back
How it starts
One DNS record on your side
- 1
Write to us
The address you want, such as go.yourcompany.com, and where it runs.
- 2
Add one record
Where your domain's DNS is kept:
Name Type Value go CNAME het-01.dopecode.com. go A your server's address - 3
We install it
One command on our side: the service, nginx, the certificate, daily backups and the country database.
- 4
Make the first account
You get the address that makes your owner, once. They add everyone else; there is no sign-up.
Where the data goes
Into one database of your organisation's, on the server your goto runs on, and nowhere else.
A click keeps
- its time
- the referring site's name
- the country
- the kind of device, its system and browser
- the first language the browser asks for
- whether it came by QR code
Never kept
- the visitor's address: it tells the country and the visitor of the day, and is dropped
- a visitor from one day to the next: each day's count starts fresh
- a cookie or a script on a visit that is sent straight on
- an access log in nginx in front of goto
Questions
Before you write
Who can see our links and clicks?
The people you add, and nobody else. Your goto has its own database, its own process and its own system user; no other organisation's goto can read it. On your own server, nothing leaves it.
What does it keep about a visitor?
The time, the referring site's name, the country, the kind of device, the system and browser, the first language the browser asks for, and whether it was a scan. The address is used to tell the country and the visitor of the day, then dropped. A visit sent straight on gets no cookie and runs no script.
Can we bring the links we have?
Yes: a CSV of links goes in from the settings, including the export of another shortener such as Bitly's. Slugs are kept as they were.
Can we leave?
At any time. Every link and every click comes out as CSV, and the API gives the rest. On your own server the database file is yours.
What does our own server need?
Linux with systemd, nginx and certbot, on x86_64 or arm64, and ports 80 and 443 for the certificate. goto itself takes about 50 MB of memory. We install it over SSH as root.
Who keeps it up to date?
We do, on our server or on yours. Each release starts beside the one before; if it does not answer its health check, the one before is put back.
Where do we sign in?
At your own goto, go.yourcompany.com/-/login: the people your owner adds sign in there, and nowhere else. This page only says what goto is.
Can our team use it from scripts?
Every page has an API behind it: links, analytics and QR codes as JSON with a key, at /-/api/v1. The shell has goto link add, imports and exports.
Your short links, on your own domain
Write to hello@dopecode.com with the address you want and where it should run. We answer with what it costs and when it can be live.