runsonwhat

tama's tech stack

What does tama use?

tama (tama.computer) uses at least 7 tools we can see from public records, including PropelAuth for sign-in, Amazon CloudFront for content delivery and Let's Encrypt for security. Last checked .

Re-check liveVisit tama.computer
Tools found
7
Categories
6
Layers
3 of 5
Last checked
Oct 2026

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

CDN & Edge

DNS

Application

3 tools, what the product is built with

Auth & Identity

AI

Media & UI

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Companies like tama also use

Tools common among companies with a similar stack that we haven't found at tama.

Companies with a stack like tama's

Ranked by shared tools, with rare tools counting more.

tama tech stack FAQ

What tools does tama use?

As of October 2026, runsonwhat has found 7 tools at tama (tama.computer) in public records. Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Google Fonts and PropelAuth. Company Ops: Let's Encrypt and Amazon Trust Services. Last checked October 9, 2026.

What does tama use for login and identity?

tama uses PropelAuth for sign-in and identity, according to runsonwhat (October 2026). runsonwhat found PropelAuth through a subdomain that points at PropelAuth. PropelAuth is used by 122 companies runsonwhat tracks.

Does tama use Google Fonts?

Yes. runsonwhat found Google Fonts at tama through Google Fonts code on tama.computer. Google Fonts is a Media & UI tool used by 765,353 companies runsonwhat tracks.

Which companies have a tech stack similar to tama's?

The companies with the stacks most like tama's are Downlink, LaunchFlow, Cartage and Niju, according to runsonwhat (October 2026). Each shares 1 to 3 tools with tama, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what tama uses?

runsonwhat reads public records only. Of the 7 tools at tama, 3 were found through DNS records, 2 through code on tama.computer, 1 through website configuration files and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and tama.computer 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.