runsonwhat

Lecture to Book's tech stack

What does Lecture to Book use?

Lecture to Book (lecturetobook.com) uses at least 12 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics, Stripe for payments and Cloudflare for content delivery. Last checked .

“Turn lecture recordings into polished, editable books — chapters written and figures pulled from your slides, exported as PDF and ePub.”

Tools found
12
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Lecture to Book'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

3 tools, where the bytes are served from

Application

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Email Delivery

Lecture to Book tech stack FAQ

What tools does Lecture to Book use?

We've found 12 tools at Lecture to Book (lecturetobook.com). Edge & Hosting: Cloudflare, Amazon CloudFront and Amazon Web Services. Application: Google Fonts, Stripe and Google Gemini. Data & Observability: Google Analytics and Microsoft Clarity. Go-to-market: Google Ads and ChatGPT Ads. Company Ops: Amazon SES. Last checked October 2, 2026.

What cloud does Lecture to Book run on?

Lecture to Book uses Amazon Web Services for hosting. We found Amazon Web Services through subprocessor list.

What payment provider does Lecture to Book use?

Lecture to Book uses Stripe for payments. We found Stripe through subprocessor list.

What analytics tools does Lecture to Book use?

Lecture to Book uses Google Analytics and Microsoft Clarity for analytics. We found Google Analytics through website code.

Does Lecture to Book use Cloudflare?

Yes. We found Cloudflare at Lecture to Book through email records, DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Lecture to Book uses?

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