Opportunities › Internal reverse proxy for private networks › Proposed app
Innername
Named HTTPS addresses for devices on private networks, with no proxy cluster
- Score
- 47
- confidence 56
- Evidence
- 6
- items on the page
- Rivals
- 2
- named in sources
- First version
- 60 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2004
- Mature market · AI estimate
ScreensConcept
Desktop app: DevOps engineers manage device naming, DNS records and network configuration from a dashboard at a desk. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Sites
Services named148
About this appAI proposal
Innername gives every internal device and service at a customer site or branch office a real name, like printer.acme.internal, with HTTPS that works. You define the name once. Innername creates the DNS record, issues the certificate and routes traffic to the right IP and port. Nobody types an address with a port number again.
It is built for MSP engineers and sysadmins who manage many separate networks. Each site is its own namespace, so two customers who both use 192.168.1.10 do not collide. Services on odd ports such as 8443 or 9090 get a clean name.
There is no public reverse proxy and no nginx cluster to run. A small agent at each site does the work, and a web console shows what is named, where, and whether its certificate is healthy.
- Tagline
- Give every internal service a name. Skip the proxy cluster.
- Voice
- PlainPreciseCalm
- Why this name
- It says what the product does: names for things on the inside of a network. Two plain words joined, easy to say aloud on a support call.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Names instead of IP and port
Map a name to any internal IP and port. Users open https://nas.siteA.internal and never see 8443 or an address.
No member yet
Automatic DNS records
Records are created and removed when you add or retire a service. No hand-edited zone files or shared spreadsheets.
No member yet
Automatic HTTPS certificates
Certificates are issued and renewed for each name. The console flags any that are close to expiry.
No member yet
Per-site namespaces
Overlapping IP ranges across customers stay separate, because each name resolves only inside its own site scope.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F5F5BDeep Teal · primary#F4F1EAPaper · surface#1F2A2EInk · text#D9822BAmber · accent#3B6EA5Slate Blue · data#B3402FSignal Red · warning
Typography
Aa
Innername
PricingAI proposal
Based on Netbird's pricing page: a free plan, two paid plans from €6 to €12 by usage, and prices on request for larger customers. The USD figures and the per-site unit are starting points to test.
Free
Free
- 1 site
- Up to 5 named services
- Automatic DNS and HTTPS
Team
$6 a month
- Per site, billed monthly
- Up to 25 named services per site
- Discovery and CSV import
- Health checks and expiry alerts
MSP
$12 a month
- Per site, billed monthly
- Unlimited named services per site
- Team and customer access roles
- Audit log
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Partners and integrations. List it as an add-on for private network and remote-access tools, using their open APIs or plugin points. Admins of those tools who hit the port and IP problem find it where they already manage peers.
- Do they become customers?
- Admins reached this way are the buyers, since they run the networks. To test: how many who try the free tier add a second site, and whether partners allow listing.
- First customers
- Small MSPs with 10 to 50 customer sites, where one or two engineers manage overlapping IP ranges and non-standard ports for cameras, NAS devices and line-of-business apps.
- Where to reach them
- Open issue threads: Reply to the people on the GitHub issue and similar threads with a working demo, and invite them to a free pilot.
- MSP communities: Post a walkthrough of naming a device at a client site in sysadmin and MSP forums, with a free single-site tier.
- Private network user groups: Offer setup help to admins of private network tools who ask about internal DNS and HTTPS.
- First milestone
- Five MSPs each running at least three sites and ten named services, with two of them paying within 60 days.
Why people already pay for this
- VerifiedOpen GitHub issue has 50 reactions and 20 comments
- Public claimOrganizations want to access devices and services at customer locations via DNS queries without port numbers or IP management
- Public claimExisting reverse proxy solutions require unnecessary complexity (nginx with proxy clusters) for internal-only use
- Public claimIP-based resource exposure is inadequate because it does not handle non-standard ports and fails when IPs conflict across networks
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Site agentSmall cross-platform agent that runs at each siteResolves names and routes to internal IPs and ports inside the private network, with no public exposure.
- This app · Internal DNSAuthoritative DNS service for per-site zonesCreates and removes records automatically and keeps overlapping IP ranges scoped to each site.
RisksAI inference
- TechnicalDevices must trust the certificates and use the site's DNS. Client setup, such as a private CA or resolver settings, may be the hardest part to make painless on mixed laptops and phones.
- PlatformPrivate network vendors, including the one named in the evidence, could add a built-in internal proxy. The demand signal is one open issue and may be served by that vendor.
- CommercialIt is unproven that MSPs will pay for a separate tool rather than wait for their network software to add the feature, or use free proxies.
- TechnicalA standalone agent needs a network path into each site. Without integration with an existing private network, it may add a second thing to install and secure.
- DataThe control plane holds a map of customers' internal devices and names. A breach would be sensitive, so security review and clear data handling are required before sales.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.