runsonwhat

Terminal's tech stack

What does Terminal use?

Terminal (terminalenergia.ee) uses at least 19 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and OneSignal for marketing. Last checked .

Industry
Oil & Gas
Size
201–1,000 employees
Based in
Kärkna, Estonia
Founded
1968
LinkedIn
Company page
Tools found
19
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

4 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

6 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Email Delivery

Dev Tools

Terminal tech stack FAQ

What tools does Terminal use?

We've found 19 tools at Terminal (terminalenergia.ee). Edge & Hosting: Amazon Route 53. Application: jQuery, Vimeo and YouTube. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365, Atlassian and Amazon SES. Last checked October 4, 2026.

What email provider does Terminal use?

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

What analytics tools does Terminal use?

Terminal uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

What CMS does Terminal use?

Terminal uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.

What marketing software does Terminal use?

Terminal uses OneSignal for marketing. We found OneSignal through website code.

Does Terminal use Microsoft 365?

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

How does runsonwhat know what Terminal uses?

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