runsonwhat

A Restaurant's tech stack

What does A Restaurant use?

A Restaurant (arestaurantnb.com) uses at least 7 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Mailchimp for marketing. Last checked .

Industry
Healthcare
Size
11–50 employees
Based in
Crestline, United States
LinkedIn
Company page
Tools found
7
Categories
6
Layers
4 of 5
Last checked
Oct 2026

A Restaurant'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

CDN & Edge

Data & Observability

1 tool, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

A Restaurant tech stack FAQ

What tools does A Restaurant use?

We've found 7 tools at A Restaurant (arestaurantnb.com). Edge & Hosting: Cloudflare. Data & Observability: Google Analytics. Go-to-market: WordPress, Yoast SEO and Mailchimp. Company Ops: Google Workspace and UserWay. Last checked October 6, 2026.

What email provider does A Restaurant use?

A Restaurant uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does A Restaurant use?

A Restaurant uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does A Restaurant use?

A Restaurant uses WordPress and Yoast SEO for its website. We found WordPress through website code.

What marketing software does A Restaurant use?

A Restaurant uses Mailchimp for marketing. We found Mailchimp through website code.

Does A Restaurant use Google Analytics?

Yes. We found Google Analytics at A Restaurant through website code. Google Analytics is used by 724,245 companies we track.

How does runsonwhat know what A Restaurant uses?

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