Your Domain, Your Data: Building a Link Platform You Own

Every organization sends links. Campaigns, product launches, QR codes on packaging, SMS reminders, invoices, internal documentation, event badges. Most teams rent the infrastructure behind those links from a third party, and for a while that feels convenient.

Then the renewal arrives. Per-seat pricing goes up. A plan limit appears. A link that mattered to a campaign stops resolving. Someone in legal asks where the click data is stored, and nobody can answer with certainty. The short links your customers see carry someone else's brand, on someone else's domain.

There is a better option: own the platform.

We can build and deploy the same link management application that powers NanoURL for your organization, on your domain, with your data in your own cloud account.

What we build for you

This is not a from-scratch experiment. The platform is already in production, so the work is configuration, branding, deployment, and handover rather than years of development.

A typical build includes:

• Your short domain — for example go.yourcompany.com, with your SSL certificates and DNS under your control.
• Your brand — dashboard, emails, and redirects styled for your organization, with no NanoURL branding unless you want it.
• Link management — custom slugs, expiration dates, archive and restore, bulk actions, and workspace organization.
• QR codes — generated for any link, downloadable in formats ready for print and packaging.
• Click analytics — total clicks, referrers, devices, and geography, reported on your own data.
• A documented REST API — so your product, CMS, and internal tools can create and manage links programmatically.
• Access control — user roles and workspaces so marketing, support, and engineering can share one platform without stepping on each other.
• Data export — your links and click history, exportable at any time.

You get the finished application, the deployment configuration, administrative documentation, and a team that knows how to keep it running.

Why owning it usually costs less than renting

Rented link tools charge in ways that compound: per user, per link, per QR code, per analytics tier, per integration. Add a second tool for QR design and a third for campaign attribution, and the stack grows faster than the traffic does.

Owning the platform changes the shape of the cost:

• One build fee instead of an endless subscription ladder. You pay once to have the application configured and deployed for your organization.
• No per-seat tax. Invite the people who need access without a procurement conversation.
• No per-link overage. A viral campaign does not produce a surprise invoice.
• One platform instead of three. Link management, QR codes, and click analytics live in the same place.
• Predictable support. A straightforward support fee covers monitoring, updates, and help, so budgeting is boring in the best way.

For many organizations, the build pays for itself by replacing overlapping subscriptions and removing the annual price increase cycle. We will model your current spend against the ownership cost during discovery, so the comparison is based on your numbers rather than ours.

You own the data

This is the part that matters most, and it is worth being precise about.

When we deploy for you, the application runs in your cloud account. You hold the keys, you control access, and you decide where data lives.

• Your database. Links, workspaces, and click events live in infrastructure you own — not in a shared multi-tenant system.
• Your retention rules. Keep click data for 30 days or 30 months. Delete it on request. Export it whenever you like.
• Your compliance posture. Data residency, audit logging, encryption, and access reviews follow your policies, because the controls are in your account.
• No data resale, ever. Your click data is not pooled, enriched, or sold. It is not used to train anything.
• No lock-in. You receive the application, the deployment configuration, and the documentation. If you ever want to run it without us, you can.

Owning the data also means owning the domain. Your short links keep your brand, survive vendor changes, and remain under your DNS control.

Two ways to deploy

The same application can run in very different environments. We scope the right one with you, and you can start lean and move later.

Option 1: Lean managed deployment

A managed deployment on shared infrastructure that we run for you. Your domain, your application, no servers for your team to patch, and no cloud account to set up.

• Fast to launch — typically days, not quarters.
• Minimal operations — we handle hosting, updates, and monitoring; you handle the links.
• Entry-level capacity included — the build includes a shared capacity tier that covers everyday marketing, QR, and internal link traffic. There is no separate hosting bill to manage at launch.
• Upgrade when you need it — if traffic grows or you need higher limits and more consistent performance, we move you to a higher-capacity tier for a small additional fee.
• Lowest total cost of ownership — no idle infrastructure and no dedicated operations headcount.

The trade-off: shared capacity is a good fit for normal traffic patterns, but it is not designed for sustained high-volume redirects or strict infrastructure isolation. Organizations with heavy load, regulatory requirements, or an existing cloud commitment usually choose Option 2.

This is the option most teams start with. It delivers the ownership benefits — your domain, your data, your application — without the operational overhead of running servers.

Option 2: AWS enterprise deployment

For organizations that need their link platform inside an existing AWS footprint, with enterprise security controls and procurement-friendly architecture.

• Runs in your AWS account — VPC, private subnets, and security groups you already govern.
• Enterprise security — AWS WAF, Shield Advanced, KMS-managed encryption, Secrets Manager, and least-privilege IAM.
• Audit and detection — CloudTrail, GuardDuty, AWS Config, and Security Hub wired into your existing monitoring.
• Identity integration — SSO through your identity provider, with role-based access aligned to your org structure.
• Resilience — Multi-AZ database, automated backups, and a documented recovery plan.
• Observability — CloudWatch metrics, logs, and alarms that feed your existing on-call process.
• Compliance-friendly — architecture designed to support your SOC 2, ISO 27001, or HIPAA program, with the evidence trail your auditors expect.

This option costs more to build and operate, because you are paying for dedicated infrastructure, deeper security controls, and more operational rigor. In exchange you get maximum control, a familiar procurement path, and the ability to use existing AWS commitments.

How they compare

Both options run the same application. The difference is where the controls live and how much infrastructure you want to own.

How pricing works

We quote every engagement individually, in USD, because scope varies. The model has three parts.

1. One-time build fee

Covers discovery, branding, domain and DNS setup, deployment, configuration, migration of existing links, testing, and handover with documentation. The quote reflects the deployment option, the number of workspaces and users, SSO requirements, data migration volume, and any custom integration work.

2. Ongoing support fee

A monthly or annual fee for monitoring, security updates, dependency upgrades, backups, and support. Optional service-level agreements are available if you need guaranteed response times. This is the fee that keeps the platform healthy after launch.

3. Future enhancements at a marginal fee

The platform keeps evolving. When a new capability ships in a future NanoURL release, we can bring it to your instance for a marginal fee rather than charging you to rebuild it. If you need something bespoke, we scope it separately and tell you honestly whether it belongs in your instance or in the shared roadmap.

There is no per-seat pricing and no per-link pricing. If your traffic doubles, your bill does not.

What the process looks like

1. Discovery call — 30 minutes on your use cases, domain, security requirements, and current spend.
2. Scoped proposal — a fixed build quote, a support plan, and a recommended deployment option.
3. Build and configure — branding, domain, analytics, roles, and integrations. Typically one to three weeks for the lean option, three to six for AWS.
4. Migration — import existing links and map old short URLs so nothing breaks.
5. Launch — go live on your domain with monitoring and backups in place.
6. Support and roadmap — ongoing maintenance, plus optional enhancements as the platform evolves.

Questions we hear

Can we keep our existing short links? Yes. We import them and preserve redirects, so printed QR codes and old campaigns keep working.

Do we own the source code? Yes. The application and deployment configuration are handed over with documentation.

Can we start lean and move to AWS later? Yes. The application is the same; the migration is a planned project, not a rewrite.

What if we need a feature that does not exist yet? We scope it. If it is part of a future release, it comes to you at a marginal fee. If it is custom, you get a clear quote before any work starts.

Is our data used for anything else? No. It stays in your account and is never resold or pooled.

What happens if we stop working with you? You keep the application, the data, and the documentation. The platform keeps running in your account.

Let's talk about your domain

If your organization is paying for link management, QR codes, and analytics across multiple tools — or if you simply want your links on your own domain with your data under your control — we should talk.

Send a note to support@nanourl.link or use the contact page with a sentence about your use case and your preferred deployment option. We will come back with a scoped quote in USD, a timeline, and an honest recommendation about which option fits.

Same platform. Your domain. Your data.