Filadelfia Oslo's tech stack
What does Filadelfia Oslo use?
Filadelfia Oslo (filadelfia.no) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Umami for analytics and Sanity for its website. Last checked .
- Industry
- Activities of Religious Organisations
- Size
- 11–50 employees
- Based in
- Norway
- Founded
- 1916
- Tools found
- 9
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Filadelfia Oslo'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
Hosting & Cloud
Application
3 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Filadelfia Oslo tech stack FAQ
What tools does Filadelfia Oslo use?
We've found 9 tools at Filadelfia Oslo (filadelfia.no). Edge & Hosting: Vercel. Application: React, Tailwind CSS and Next.js. Data & Observability: Umami. Go-to-market: Sanity. Company Ops: Google Workspace and SendGrid. Last checked October 4, 2026.
What cloud does Filadelfia Oslo run on?
Filadelfia Oslo uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.
What email provider does Filadelfia Oslo use?
Filadelfia Oslo uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What analytics tools does Filadelfia Oslo use?
Filadelfia Oslo uses Umami for analytics. We found Umami through website code.
What CMS does Filadelfia Oslo use?
Filadelfia Oslo uses Sanity for its website. We found Sanity through website code.
Does Filadelfia Oslo use Google Workspace?
Yes. We found Google Workspace at Filadelfia Oslo through email records and website code. Google Workspace is used by 187,473 companies we track.
How does runsonwhat know what Filadelfia Oslo uses?
We read public traces only: Filadelfia Oslo'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.