runsonwhat

Morikami Museum and Japanese Gardens's tech stack

What does Morikami Museum and Japanese Gardens use?

Morikami Museum and Japanese Gardens (morikami.org) uses at least 19 tools we can see from public records, including Kinsta for hosting, Google Analytics for analytics, authorize.net for payments and WordPress for its website. Last checked .

Industry
Museums and Institutions
Size
51–200 employees
Based in
Delray Beach, United States
Founded
1977
LinkedIn
Company page
Tools found
19
Categories
11
Layers
5 of 5
Last checked
Oct 2026

Morikami Museum and Japanese Gardens'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

2 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Data & Observability

2 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Morikami Museum and Japanese Gardens tech stack FAQ

What tools does Morikami Museum and Japanese Gardens use?

As of October 2026, runsonwhat has found 19 tools at Morikami Museum and Japanese Gardens (morikami.org) in public records. Edge & Hosting: Cloudflare and Kinsta. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: reCAPTCHA and SendGrid. Last checked October 20, 2026.

What cloud does Morikami Museum and Japanese Gardens run on?

Morikami Museum and Japanese Gardens uses Kinsta for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Kinsta through Kinsta code on morikami.org. Kinsta is used by 12,764 companies runsonwhat tracks.

What payment provider does Morikami Museum and Japanese Gardens use?

Morikami Museum and Japanese Gardens uses authorize.net for payments and billing, alongside SkyVerge, according to runsonwhat (October 2026). runsonwhat found authorize.net through authorize.net code on morikami.org. authorize.net is used by 2,110 companies runsonwhat tracks.

What analytics tools does Morikami Museum and Japanese Gardens use?

Morikami Museum and Japanese Gardens uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on morikami.org. Google Analytics is used by 864,154 companies runsonwhat tracks.

What is Morikami Museum and Japanese Gardens's website built with?

Morikami Museum and Japanese Gardens uses WordPress for its website, alongside WooCommerce, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on morikami.org. WordPress is used by 588,914 companies runsonwhat tracks.

What marketing software does Morikami Museum and Japanese Gardens use?

Morikami Museum and Japanese Gardens uses Mailchimp for marketing, according to runsonwhat (October 2026). runsonwhat found Mailchimp through Mailchimp code on morikami.org. Mailchimp is used by 113,930 companies runsonwhat tracks.

Does Morikami Museum and Japanese Gardens use jQuery?

Yes. runsonwhat found jQuery at Morikami Museum and Japanese Gardens through jQuery code on morikami.org. jQuery is a Frontend tool used by 905,671 companies runsonwhat tracks.

Which companies have a tech stack similar to Morikami Museum and Japanese Gardens's?

The companies with the stacks most like Morikami Museum and Japanese Gardens' are American Civil War Museum, North Carolina Association Of County Commissioners, SubroClaims and Bay Manufacturing, according to runsonwhat (October 2026). Each shares 10 to 13 tools with Morikami Museum and Japanese Gardens, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Morikami Museum and Japanese Gardens uses?

runsonwhat reads public records only. Of the 19 tools at Morikami Museum and Japanese Gardens, 17 were found through code on morikami.org, 1 through DNS records and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and morikami.org about 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.