Infrastructure built for what you actually run
Generic cloud platforms are built for generic workloads. We built Taglinko for the one marketers rely on every day, a server-side tracking container on their own domain, without the bloat of tools you'll never touch.
One container
Example accountYour usage, always in view
Watch requests, domains and events in real time.
Illustration of a Pro plan (500,000 requests a month, 1 domain). Figures are an example, not live data.
- 1DashboardContainers, domains, logs and billing
- 15KFree requests a monthOn every free container
- $0To startFree Server GTM plan, no card
- 3Global regionsNorth America, Europe, Dhaka (BDIX)
Our mission
Build the platform we wanted to use ourselves
We kept running into the same problem: growth agencies and independent marketers needed server-side tagging on their own domain, but every platform we tried either priced it unpredictably, buried limits in fine print, or was built for developers. So we built the platform we wanted to use ourselves: simple request-based plans, one bill, and a dashboard that actually shows you what's running.
Company history
How Taglinko got here
The releases that shaped the platform, in the order they shipped.
- 01
First release
Sign-up, a deploy engine, Stripe billing and a dashboard.
- 02
Server GTM gets its own plans
Dedicated pages and plans, and a short path from the landing page to a running container.
- 03
Affiliate and Partner program
Every user gets a referral link. Vetted partners earn a higher recurring commission.
- 04
Pick your region
Containers can be placed in North America, Europe or Dhaka (BDIX).
- 05
Backups and bKash Payment
Nightly encrypted backups with restore, and bKash Payment for customers in Bangladesh.
How we evolve
Small steps, checked on real servers
Taglinko changes every week. This is how we keep it from breaking while it does.
- 01
We listen
Questions that reach support become Help Center answers and docs. What customers ask decides what we write and what we fix.
- 02
We change one thing at a time
Each change is small, comes with a way back, and new behaviour is switched on only when it has proven itself.
- 03
We test on a real server
Features are tried on a real stack, not just on a laptop, so the docs describe what actually happens.
- 04
We back up before we touch anything
Before a risky change we make sure the data can be restored. The restore is tested, not assumed.
What we built
One platform, the workloads that matter
Everything on Taglinko is here because marketers actually use it.
Managed server-side GTM
Google's official server container on your own first-party domain, with a Custom Loader, Cookie Keeper and live request metrics.
Live usage, always visible
Your Usage page shows your request count, so limits are never a surprise.
Support from people
Email hello@taglinko.com. We typically reply within one business day.
Built for teams
Invite teammates as Viewer, Developer or Admin, and keep billing with the account owner.
Infrastructure
Where your containers run, and what protects them
You work with a dashboard. We run the servers, certificates, routing, monitoring and backups behind it.
- 01
3 global regions
Servers in North America, Europe and Dhaka (BDIX). You choose where a container runs.
- 02
Isolated containers
Each container runs on its own network, with automatic SSL on your domains.
- 03
Nightly encrypted backups
Customer data is saved every night, encrypted before they leave the server, and kept off the server at a different provider. A weekly restore test checks that they open.
- 04
Secrets stay secret
Passwords and keys live in settings, not in our code, and every backup file is encrypted with its own key.
Technology
Proven parts, assembled for operators
We use well-known open tools where they are the right answer, and build the dashboard around them.
- TrackingGoogle's official server-side GTM containerFirst-party domainsLive request metrics
- PaymentsStripe for customers worldwidebKash Payment for customers in Bangladesh
- Our own codeA NestJS APIA Next.js dashboard and websitePostgreSQL
Team
The people behind Taglinko
Taglinko is built by its founder, and every support email gets a real reply.
Mahmudul Hasan
Founder
Builds the platform, writes the docs and answers the email. If something on Taglinko does not work the way a page says it should, that is a bug and the founder wants to hear about it.
Articles by MahmudulReach us
hello@taglinko.com
Mon to Fri, 9am to 6pm BD Time
We usually reply within one business day
House 2, Road 3, Block C, Nobodoy Housing, Mohammadpur, Dhaka, Bangladesh
Culture
How we work, and what we will not do
- 01
Plain language
Docs and pages say what a feature really does, in words you would use yourself.
- 02
Honest numbers
We show your real limits and usage, and we do not invent statistics or customers to look bigger.
- 03
Your data comes first
We protect it before we improve anything else, and we test that it can come back.
- 04
Support from a person
You email a human who knows the product, not a script.
- 05
Check it, then say it
We try a thing on a real server before we write that it works.
- 06
Built for operators
We design for the person running the business, not only the person writing the Dockerfile.