RubyGarage's tech stack
What does RubyGarage use?
RubyGarage (rubygarage.org) uses at least 13 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Zoho for sales and Ortto for marketing. Last checked .
- Industry
- IT Services
- Size
- 51–200 employees
- Based in
- Tallinn, Estonia
- Founded
- 2011
- Company page
- Tools found
- 13
- Categories
- 8
- Layers
- 3 of 5
- Last checked
- Oct 2026
RubyGarage'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
Hosting & Cloud
CDN & Edge
Go-to-market
6 tools, how they find and keep customers
Marketing
Ads & Pixels
Sales & CRM
Company Ops
4 tools, what the team runs on day to day
RubyGarage tech stack FAQ
What tools does RubyGarage use?
We've found 13 tools at RubyGarage (rubygarage.org). Edge & Hosting: Cloudflare, Google Cloud and Amazon CloudFront. Go-to-market: Meta Pixel, Zoho and Calendly. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 6, 2026.
What cloud does RubyGarage run on?
RubyGarage uses Google Cloud for hosting. We found Google Cloud through custom domain.
What CRM does RubyGarage use?
RubyGarage uses Zoho, Calendly and Pipedrive for sales and CRM. We found Zoho through DNS verification records.
What email provider does RubyGarage use?
RubyGarage uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What marketing software does RubyGarage use?
RubyGarage uses Ortto for marketing. We found Ortto through email records.
Does RubyGarage use Microsoft 365?
Yes. We found Microsoft 365 at RubyGarage through DNS verification records. Microsoft 365 is used by 692,910 companies we track.
How does runsonwhat know what RubyGarage uses?
We read public traces only: RubyGarage'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.