Portland, United States
Server infrastructure for InsurTech in Portland
The right server for InsurTech is decided by the work it has to do, not by the size of the plan you happen to land on. For a small InsurTech business in Portland that is about Single Core, 16 GB of memory and 100 GB of storage on VPS.
- ✓ 5 infrastructure tiers
- ✓ Sized for your workload, not a plan name
- ✓ Same price in all 24 locations
Estimated from fibre distance, not measured from Portland. Your real figure depends on your connection and route, and lands inside this range.
Choose the infrastructure for your workload
Three sizes of business, each sized from an assumed traffic figure rather than a measured one. If you know your own numbers, tell us and the estimate changes with them.
Small InsurTech Most likely here
1–10 people · ~5,000 visits a month
$164.90 USD USD
per month · VPS
- Single Core
- 16 GB RAM
- 100 GB storage
About 1.4 requests a second at peak, holding roughly 11.2 GB of working data.
Configure this build →Medium InsurTech
11–50 people · ~50,000 visits a month
$432.40 USD USD
per month · VDS
- 4 Cores
- 48 GB RAM
- 250 GB storage
- Managed
About 13.9 requests a second at peak, holding roughly 32 GB of working data.
Configure this build →Large InsurTech
51+ people · ~500,000 visits a month
$1,721.65 USD USD
per month · Dedicated Server
- 16 Cores
- 196 GB RAM
- 900 GB storage
- Managed
About 138.9 requests a second at peak, holding roughly 128 GB of working data.
Configure this build →These figures are assumptions stated out loud, not predictions about your business. Memory, cores and disk can all be raised on the same server later, usually within the hour, with no rebuild and no new IP address — so starting one size below the estimate is normally the cheaper mistake.
Why InsurTech size up this way
Working from about 5,000 visits a month and roughly 40,000 requests a day, about 11 GB of data needs to stay in memory to keep queries fast; and each request costs real computation rather than a cache lookup, so cores matter more here than on a typical site.
- 1.4 req/sec at peak
- 11.2 GB working set
- 4 GB/month growth
- Linux
Which tiers suit InsurTech
Including the ones that do not, and why — that is usually the more useful half.
| Infrastructure | Verdict | Why |
|---|---|---|
| Shared Hosting Managed space on a shared server | Not this one | Shared hosting cannot run background workers, queues or long-lived processes, which a SaaS application depends on. |
| VPS Flexible virtual infrastructure with full root access | Recommended | The natural home for an early-stage product: root access, your own runtime, and the ability to resize as you grow. |
| VDS Virtual server with resources pinned to you alone | Recommended | Pinned resources give you the predictable latency your customers will hold you to in an SLA. |
| Dedicated Server An entire physical server, configured to your specification | Recommended | Right once the database and the application tier are competing for the same memory on a single virtual instance. |
| Bare Metal Physical compute for sustained, demanding workloads | Workable | For platforms running their own virtualization, or holding a large working set entirely in memory. |
InsurTech workloads you can host
Pricing runs a model per quote, so the cost of a page view is real computation rather than a database read.
- Underwriting API
- Pricing models
- Digital claims flow
- Policy issuance
- Data enrichment services
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
Portland is closest to Dallas. Every marker costs the same per month.
Show all 24 locations and distances from Portland ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Americas · 9 locations | ||
| Dallas, United States | 340 miles | 8–16 ms |
| Atlanta, United States | 867 miles | 21–42 ms |
| Miami, United States | 1,066 miles | 26–51 ms |
| Chicago, United States | 1,111 miles | 27–54 ms |
| Los Angeles, United States | 1,308 miles | 32–63 ms |
| Toronto, Canada | 1,477 miles | 36–71 ms |
| Santa Clara, United States | 1,570 miles | 38–76 ms |
| New York, United States | 1,591 miles | 38–77 ms |
| Seattle, United States | 1,914 miles | 46–92 ms |
| Europe, Middle East & Africa · 8 locations | ||
| London, United Kingdom | 5,024 miles | 121–243 ms |
| Madrid, Spain | 5,174 miles | 125–250 ms |
| Amsterdam, The Netherlands | 5,194 miles | 125–251 ms |
| Stockholm, Sweden | 5,386 miles | 130–260 ms |
| Frankfurt, Germany | 5,411 miles | 131–261 ms |
| Milan, Italy | 5,594 miles | 135–270 ms |
| Bucharest, Romania | 6,299 miles | 152–304 ms |
| Tel Aviv, Israel | 7,234 miles | 175–349 ms |
| Asia-Pacific · 7 locations | ||
| Tokyo, Japan | 6,689 miles | 161–323 ms |
| Hong Kong, China | 8,382 miles | 202–405 ms |
| Sydney, Australia | 8,426 miles | 203–407 ms |
| Delhi NCR, India | 8,523 miles | 206–412 ms |
| Kolkata, India | 8,930 miles | 216–431 ms |
| Mumbai, India | 9,127 miles | 220–441 ms |
| Singapore | 9,978 miles | 241–482 ms |
Distances are from Portland. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
InsurTech in Portland
Finance & Insurance is one of the sectors Portland is known for, so this is a workload we are asked about here more than most.
The closest of our 24 data centres to Portland is Dallas, about 340 miles away. The price is the same in all 24 locations, so distance is the only variable worth optimising.
Portland has a population of about 16,116, which is why the small build above is the one most likely to fit a InsurTech business here — though the other two are a click away if it does not. Local time is America/Chicago, so routine maintenance and backups are scheduled against your overnight rather than ours.
Data stays in the jurisdiction you choose, which matters if you are working to state privacy laws such as the CCPA. Pricing is quoted in USD, and the figure is the same wherever the machine physically sits.
Network reach from Portland
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Portland | Estimated round trip |
|---|---|---|
| Dallasamericas | 340 miles | 8–16 ms |
| Atlantaamericas | 867 miles | 21–42 ms |
| Miamiamericas | 1,066 miles | 26–51 ms |
Portland sits in Texas, and every one of our 24 locations costs the same — so the only thing worth optimising is which of them your users are closest to. At the small size assumed above, that is roughly 40,000 requests a day crossing that link.
InsurTech hosting in Portland — FAQs
What size server does a InsurTech business in Portland, TX need?
Where would the server for my Portland, TX business actually run?
Is a VPS enough for InsurTech, or do we need a dedicated server?
Can you host underwriting API for us?
Can we start smaller and grow?
Other industries in Portland
Same city, different workload.
InsurTech hosting nearby
The same workload, in the nearest cities.