runsonwhat

memctl/memctl's tech stack

What does memctl/memctl use?

memctl/memctl (memctl.com) uses at least 8 tools we can see from public records, including GitHub Pages for hosting, Stripe for payments, Better Stack for monitoring and Cloudflare for content delivery. Last checked .

Re-check liveVisit memctl.com
Tools found
8
Categories
8
Layers
5 of 5
Last checked
Oct 2026

memctl/memctl'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

Application

2 tools, what the product is built with

AI

Payments & Billing

Data & Observability

1 tool, what they measure and store

Monitoring

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Companies like memctl/memctl also use

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

Companies with a stack like memctl/memctl's

Ranked by shared tools, with rare tools counting more.

memctl/memctl tech stack FAQ

What tools does memctl/memctl use?

We've found 8 tools at memctl/memctl (memctl.com). Edge & Hosting: Cloudflare and GitHub Pages. Application: Stripe. Data & Observability: Better Stack. Company Ops: Resend and HackerOne. Last checked October 2, 2026.

What cloud does memctl/memctl run on?

memctl/memctl uses GitHub Pages for hosting. We found GitHub Pages through website code.

What payment provider does memctl/memctl use?

memctl/memctl uses Stripe for payments. We found Stripe through DNS verification records.

Does memctl/memctl use Cloudflare?

Yes. We found Cloudflare at memctl/memctl through DNS records. Cloudflare is used by 518,135 companies we track.

How does runsonwhat know what memctl/memctl uses?

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