runsonwhat

lp.systemdb's tech stack

What does lp.systemdb use?

lp.systemdb (systemdb.com.br) uses at least 10 tools we can see from public records, including DigitalOcean for hosting, Microsoft 365 for email and documents, WordPress for its website and RD Station for marketing. Last checked .

Industry
IT Services
Size
11–50 employees
Based in
São Paulo, Brazil
Founded
2007
LinkedIn
Company page
Tools found
10
Categories
7
Layers
4 of 5
Last checked
Oct 2026

lp.systemdb'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

Hosting & Cloud

Application

3 tools, what the product is built with

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

lp.systemdb tech stack FAQ

What tools does lp.systemdb use?

We've found 10 tools at lp.systemdb (systemdb.com.br). Edge & Hosting: DigitalOcean. Application: jQuery, YouTube and Vimeo. Go-to-market: WordPress, Yoast SEO and RD Station. Company Ops: Microsoft 365 and SendGrid. Last checked October 6, 2026.

What cloud does lp.systemdb run on?

lp.systemdb uses DigitalOcean for hosting. We found DigitalOcean through custom domain.

What email provider does lp.systemdb use?

lp.systemdb uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and DNS verification records.

What CMS does lp.systemdb use?

lp.systemdb uses WordPress and Yoast SEO for its website. We found WordPress through website code.

What marketing software does lp.systemdb use?

lp.systemdb uses RD Station for marketing. We found RD Station through email records.

Does lp.systemdb use Microsoft 365?

Yes. We found Microsoft 365 at lp.systemdb through email records and DNS verification records. Microsoft 365 is used by 685,737 companies we track.

How does runsonwhat know what lp.systemdb uses?

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