SURF
Buying intent
49 tracked signals | Top 15 topics are below | Product and Engineering are carrying most of it.
Attention by team
LinkedIn activity, by teamWhere SURF's own people are actually spending their attention, by team, by topic. Bands run Low to High against the busiest pairing on this page, and each cell also shows how much of that team's own activity it represents.
Topics being researched
30-day windowEvery tracked topic, ranked by volume, not by our guess at what matters. Confidence is the classifier's own certainty that a signal belongs where we've filed it.
9d ago
10d ago
15d ago
25d ago
26d ago
11d ago
26d ago
17d ago
22d ago
26d ago
26d ago
26d ago
19d ago
25d ago
24d ago
Need intent for a specific topic or industry?
We track the full taxonomy across every account in the graph — including themes not shown on this page.
Who's active at SURF
verified title on fileTitles, seniority and topic straight from each person's own activity, with a LinkedIn link so you can check any of them yourself.
See everyone, not just the first 10
12 people across every department at SURF, plus a LinkedIn profile link for each.
Primary products / business lines
LinkedIn company profileSURF is a cooperative association of Dutch educational and research institutions in which the members combine their strengths. Within SURF, we work together to acquire or develop the best possible digital services, and to encourage knowledge sharing through continuous innovation. The members are the owners of SURF.
Top accounts researching SURF
names withheld on the public pageThese are companies whose own people brought up SURF unprompted, not accounts we guessed might be interested. We can't yet tell an implementation partner from a genuine buyer here, names unlock along with the buyer profile below.
151,426 companies · 839,012 people are researching Artificial Intelligence
SURF's own team shows 11 signals on this topic. No one outside SURF has been seen researching the company by name yet — so this is the market it sits in, not a list of its buyers.
- Open Source11,773 cos · 38,647 people
- Graphic Design2,572 cos · 12,749 people
Buyer profile
company size · seniorityCompany size and how senior the people involved are, the two things that decide whether this is a real deal. Competitor overlap isn't computed yet for this account.
Buying committee functions
Employee job titles (LinkedIn)Engineering — 1 person; IT — 1 person
What's been said
public posts by SURF's teamNo public post naming SURF has surfaced in the past year, so this is what SURF's own team is posting about publicly — their topics, in their words.
Yesterday’s 3rd Irish Workshop on Fibre Optic Sensing in Dublin was exactly the kind of event I enjoy: practical, collaborative, and clearly helping build a strong fiber sensing community. Thanks to Asiera , Dublin Institute for Advanced Studies and Trinity College Dublin for the invitation and warm welcome. I joined on behalf of SURF to share a Dutch perspective on optical fiber sensing, and to explore where research collaboration around fiber sensing could take us next. A useful reminder from the day: we often say DAS, or Distributed Acoustic Sensing, but technically it is Distributed Dynamic Strain Sensing. Less catchy. More correct. The eternal struggle of science. The program covered everything from seismic monitoring and offshore sensing to city sensing, temperature sensing and storm tracking. A good reminder of how diverse this field has become. Great to see the Irish fiber sensing community in such good shape. I left Dublin with new ideas, useful contacts, and a boosted appreciation for how much can be learned from a strand of glass. #FiberSensing #DAS #ResearchInfrastructure #Geophysics
May 2026Three popular packages got hijacked recently. All three went after the same thing: Credentials on developer machines. In my experience, most developer laptops are full of plaintext secrets: - API keys. - Database URLs. - Cloud credentials. - Personal access tokens. - SSH keys. - Coding agent files There have been several supply chain attacks targeting packages many of us use every day across projects, including LiteLLM, TanStack, and Axios. The average developer machine is a treasure chest for attackers. One way to reduce the blast radius is to stop storing long-lived secrets in plaintext on disk. Did you know password managers like 1Password or BitWarden can inject secrets at runtime? For example, with the op CLI: op run --env-file .env -- npm run dev And your .env no longer needs to contain the actual secret values. Your local dev environment should not be a vault. Use a real one.
May 2026