It also started as a simple geolocation API when I first launched it over 3 years ago. Since then we've built many custom data sets and expanded to more products, including IP to company details, carrier detection, reverse IP hosting data and more. See https://ipinfo.io/products. We've been lucky enough to signup customers like Dell, Tesla, eBay, TripAdvisor, Plesk and others. Happy to chat and share notes at some point!
Thanks coderholic! :). I took a lot of inspiration from your service but built around solving a number of pain points. Would love to chat and talk sometime :)
Won't you only pay a % of the gain in price in tax? In that case you're strictly worse if it goes down in price. You'd pay less tax, yes, but as tax is % of gains you're net worse off. If this really isn't the case can you share some example numbers showing how you can be worse off with a house that's worth more?
Suppose we bought our house for $1M and now it's worth $2M. We have to pay 25% cap gains (federal + state) on $500k so it costs us $125k to move to a house of equal value. If prices were stable, we could move without taking that hit. The higher prices go, the higher the cost of moving.
What you say is true, but it misses the point, which is that big gains only help you if you actually cash out. If you're making a lateral move, or downsizing in the same area, it doesn't matter whether you're leveraged or not. A loss is still a loss.
The example is useful, thanks. I see that there's $125k of cap gains to pay for a move to a property of the same price. You're calling that a loss though, and I'm not sure I see it that way. Sure, if house prices hadn't gone up you could have moved from a $1M house to another $1M house and paid nothing. But in your example you're still $875k "in profit", so it's not really a loss, it's just a cost associated with a lateral move in the same area. If you downsize you actually realize some of those gains - of course not all of them because tax must be paid, but there's no avoiding taxes :)
We have a company details API that does exactly that at ipinfo.io - get in touch at support@ipinfo.io if you'd like more details or see https://ipinfo.io/products
Congrats on the launch! Looks very similar to my service, https://ipinfo.io :) I launched that around 3 years ago and at the time there weren't even any paid plans. It now handles close to 500 million API requests a day.
I'd recommend killing the unlimited plan - you'll lose out on revenue with that.
Good luck! Feel free to reach out to me if there's anything you think I could help with.
Thank you! And congratulations on 500m requests per day - that's insane!
Thanks for the tip on pricing, the plans are essentially guesswork at the moment until I see some real users with real usage. I checked out some other services (including yours ;) ) and saw a wide range of pricing, some that had unlimited plans and some that didn't. Will definitely be something to revisit in the future.
I think coderholic gave you a good advice. If you're on amazon with a pay per use plan, you should immediately do the math of what it's going to cost you if someone does 1M request a day.
Let's say someone who make an equivalent service, sells cheaper plans, and uses yours for example.
On point 6, find the asn, my own service https://ipinfo.io can help you there. Curl ipinfo.io/ANYIP/org and you'll get the ASN info. Also see ipinfo.io/developers for more options such as geolocation, hostname, hosted domains, and more.
Yes open sourcing it would be great. If only as example / inspiration. There are tons and tons of open source tooling and articles on building sites and services but rarely full sites with all the 'glue' around the core service that is necessary to actually operate it.
Re/ latency.at: This was probably /newest not the front page. My blog articles didn't work well on HN. But at least when launched I got on the front page. Still really hard to acquire users.
