Port City Java's tech stack
What does Port City Java use?
Port City Java (portcityjava.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents and Google Analytics for analytics. Last checked .
- Industry
- Gastronomy
- Size
- 201–1,000 employees
- Based in
- Wilmington, United States
- Founded
- 1995
- Company page
- Tools found
- 11
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Port City Java's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
1 tool, where the bytes are served from
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
Port City Java tech stack FAQ
What tools does Port City Java use?
We've found 11 tools at Port City Java (portcityjava.com). Edge & Hosting: Amazon Route 53. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365. Last checked October 3, 2026.
What email provider does Port City Java use?
Port City Java uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Port City Java use?
Port City Java uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does Port City Java use Microsoft 365?
Yes. We found Microsoft 365 at Port City Java through email records. Microsoft 365 is used by 251,927 companies we track.
How does runsonwhat know what Port City Java uses?
We read public traces only: Port City Java's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.