Plickers's tech stack
What does Plickers use?
Plickers (plickers.com) uses at least 18 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, Stripe for payments and Sentry for monitoring. Last checked .
- Industry
- Education
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Founded
- 2013
- Company page
- Tools found
- 18
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
Plickers'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
Application
4 tools, what the product is built with
Frontend
Backend & Database
Payments & Billing
Media & UI
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
8 tools, what the team runs on day to day
Email Delivery
Workspace
Plickers tech stack FAQ
What tools does Plickers use?
We've found 18 tools at Plickers (plickers.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery, Google Fonts and Stripe. Data & Observability: Sentry. Go-to-market: Zendesk and Discourse. Company Ops: Google Workspace, SendGrid and GlobalSign. Last checked October 4, 2026.
What email provider does Plickers use?
Plickers uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Plickers use for customer support?
Plickers uses Zendesk and Discourse for customer support. We found Zendesk through custom domain and email records.
What payment provider does Plickers use?
Plickers uses Stripe for payments. We found Stripe through website code.
Does Plickers use Google Workspace?
Yes. We found Google Workspace at Plickers through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Plickers uses?
We read public traces only: Plickers'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.