# Tech Stack + Hiring Signals by Domain (`tillwork/tech-stack-hiring-signals`) Actor

Give a list of company domains and get each one's tech stack (CMS, framework, analytics, payments, chat, hosting), email provider and SaaS tools from DNS records, plus whether they're hiring, how many open roles they have and in which teams.

- **URL**: https://apify.com/tillwork/tech-stack-hiring-signals.md
- **Developed by:** [Kapil sarma](https://apify.com/tillwork) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$6.00 / 1,000 domain looked ups

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Tech Stack + Hiring Signals by Domain

Enrich a list of company domains with what they run and whether they're growing. One request per company, one clean row back: their tech stack, email provider, the SaaS tools their DNS gives away, and their open roles by team. A low-cost alternative to BuiltWith or Wappalyzer lookups, with hiring data they don't have.

### What you get for each domain

- **Tech stack from the website:** about 100 technologies across CMS and site builders, ecommerce, JavaScript frameworks, analytics, ad pixels, marketing automation, live chat and support, payments, A/B testing, cookie consent, error monitoring, authentication, video, fonts, CDN, hosting and web servers. Each comes with its evidence (the header, script or tag that gave it away).
- **From DNS records:** the email provider (Google Workspace, Microsoft 365, Zoho...), the DNS host, SPF and DMARC policy, and SaaS tools the company has verified its domain with, such as Atlassian, Slack, Notion, Stripe, DocuSign, Zoom, HubSpot, SendGrid, OpenAI or Anthropic.
- **Hiring signals:** the job board they use (Greenhouse, Lever, Ashby, SmartRecruiters or Workday), number of open roles, top departments hiring, share of remote roles, and the newest posting date.
- **Social profiles** linked from the homepage (LinkedIn, X, GitHub, YouTube and more).

### Use cases

- **Sales prospecting:** find companies on a competitor's tool, or companies hiring for the team you sell to.
- **Lead scoring:** rank accounts by stack fit and hiring momentum.
- **Market research:** see which tools are common in a segment.

### Input

| Field | Example |
|---|---|
| Domains | `stripe.com`, `https://www.notion.so`, `ramp.com` |
| Check DNS records | on |
| Check hiring | on |

### Output

```json
{
  "domain": "acme.com",
  "title": "Acme: plan work together",
  "technologyCount": 14,
  "categories": {
    "JavaScript framework": ["Next.js", "React"],
    "Hosting": ["Vercel"],
    "Analytics": ["Segment", "Hotjar"],
    "Payments": ["Stripe"],
    "Collaboration": ["Atlassian", "Slack"]
  },
  "technologies": [{ "name": "Next.js", "category": "JavaScript framework", "evidence": ["page HTML"] }],
  "emailProvider": "Google Workspace",
  "dnsHost": "Cloudflare",
  "dmarcPolicy": "reject",
  "hiring": true,
  "atsProvider": "ashby",
  "openRoles": 37,
  "topDepartments": [{ "department": "Engineering", "roles": 15 }, { "department": "Sales", "roles": 9 }],
  "remoteShare": 0.41,
  "newestPostingAt": "2026-10-15T00:00:00.000Z"
}
```

### Pricing

You pay per domain looked up.

### Good to know

- Detection reads the homepage HTML, response headers and public DNS records. Tools that only load after a login, or are added later by JavaScript, may be missed.
- Hiring data comes from the company's public job board. Companies that use another applicant-tracking system show their careers page link, without a role count.
- Only public data is read. No logins and no personal data.

# Actor input Schema

## `domains` (type: `array`):

Company domains or website links, one per line, for example stripe.com or https://www.notion.so.

## `includeDns` (type: `boolean`):

Read MX, TXT and NS records to find the email provider, DNS host and SaaS tools the company has verified, such as Atlassian, Slack or Stripe.

## `includeHiring` (type: `boolean`):

Find the company's job board (Greenhouse, Lever, Ashby, SmartRecruiters or Workday) and count open roles by team.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "notion.so",
    "ramp.com"
  ],
  "includeDns": true,
  "includeHiring": true
}
```

# Actor output Schema

## `companies` (type: `string`):

Tech stack, email provider and hiring signals per domain

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "stripe.com",
        "notion.so",
        "ramp.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tillwork/tech-stack-hiring-signals").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": [
        "stripe.com",
        "notion.so",
        "ramp.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("tillwork/tech-stack-hiring-signals").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "stripe.com",
    "notion.so",
    "ramp.com"
  ]
}' |
apify call tillwork/tech-stack-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tillwork/tech-stack-hiring-signals"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/iQOBKr1G0nfJI8Jyz/builds/3orszhr6VtZZgzdme/openapi.json