runsonwhat

FoodCourt's tech stack

What does FoodCourt use?

FoodCourt (getfoodcourt.com) uses at least 12 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Zoho for sales and Freshdesk for customer support. Last checked .

“Virtual Restaurants & Stores for Africa”

Industry
Food and Beverage
Size
51–200 employees
Based in
Lagos, Nigeria
Tools found
12
Categories
9
Layers
4 of 5
Last checked
Oct 2026

FoodCourt'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

3 tools, where the bytes are served from

Application

3 tools, what the product is built with

Go-to-market

4 tools, how they find and keep customers

Ads & Pixels

Support & Docs

Company Ops

2 tools, what the team runs on day to day

Email Delivery

FoodCourt tech stack FAQ

What tools does FoodCourt use?

We've found 12 tools at FoodCourt (getfoodcourt.com). Edge & Hosting: Amazon CloudFront, Microsoft Azure and Amazon Web Services. Application: Google Fonts, Next.js and Adobe Fonts. Go-to-market: Meta Pixel, Zoho and Freshdesk. Company Ops: Microsoft 365 and Mailgun. Last checked October 2, 2026.

What cloud does FoodCourt run on?

FoodCourt uses Microsoft Azure and Amazon Web Services for hosting. We found Microsoft Azure through custom domain and DNS records.

What CRM does FoodCourt use?

FoodCourt uses Zoho and Calendly for sales and CRM. We found Zoho through DNS verification records and email records.

What email provider does FoodCourt use?

FoodCourt uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What does FoodCourt use for customer support?

FoodCourt uses Freshdesk for customer support. We found Freshdesk through website code.

Does FoodCourt use Microsoft 365?

Yes. We found Microsoft 365 at FoodCourt through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what FoodCourt uses?

We read public traces only: FoodCourt'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.