StarSling's tech stack
What does StarSling use?
StarSling (starsling.dev) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Instatus for monitoring and Cloudflare for content delivery. Last checked .
“StarSling is AI-native CI for GitHub Actions: drop-in Ubuntu runners plus agents that open optimization PRs for your workflows.”
- Industry
- Engineering, Product and Design
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Founded
- 2025
- Company page
- Tools found
- 9
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
StarSling'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
3 tools, what the product is built with
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
Workspace
Security & Compliance
StarSling tech stack FAQ
What tools does StarSling use?
We've found 9 tools at StarSling (starsling.dev). Edge & Hosting: Cloudflare and Vercel. Application: Tailwind CSS and Remix. Data & Observability: Instatus. Company Ops: Google Workspace and Oneleet. Last checked October 2, 2026.
What cloud does StarSling run on?
StarSling uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.
What email provider does StarSling use?
StarSling uses Google Workspace for email and documents. We found Google Workspace through email records.
Does StarSling use Cloudflare?
Yes. We found Cloudflare at StarSling through DNS records and email records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what StarSling uses?
We read public traces only: StarSling'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.