Launching soon · building the database

The events world is pitch dark.
We hold the light.

ConfBeacon watches the conferences in your field, has every change cleared by an editor, and ranks what is worth your season. The product is built. The database is filling right now — source by source, edition by edition.

You will not find a count of watched events on this page. We publish numbers once they are real — today they would only be a promise about a database that is still filling.

What we are doing right now

None of this is a mock-up. Everything below already runs — it just does not yet run over enough of the world to open the catalogue.

Sources

Sources vetted one at a time

Before a crawler is pointed at a site we check who publishes it, how often it changes and whether its dates hold up. One bad source poisons a whole vertical, so this is the slow part on purpose.

Editing

Every record passes a person

The machine proposes, an editor decides. That is the rule the catalogue is built on — and it is also why the database fills at the speed of reading rather than the speed of scraping.

Verticals

Opening one field at a time

A vertical opens when its sources hold up and someone is editing it. Rather than a thin catalogue of everything, we open the first fields properly — and tell you which ones.

01

Programmes change the week before

Speakers drop, stages move, prices jump. The conference website is the last to admit it.

02

“Top 50 events” lists aren't about you

They rank by the author's reach. Your market, your role and your budget never appear in them once.

03

So the call gets made late and blind

Early bird expires, flights double, and the team goes wherever it went last year.

Three steps from dark to a route

Set it once. The beacon stays lit all year.

1

Tell us where you're headed

Your market, region, role and budget. It takes a few minutes, and every answer is a filter you can change later — not a form you fill in once and never see again.

2

The beacon sweeps

Discovery walks known sources looking for events we don't have yet. The nightwatch re-reads pages already in the catalogue and files a proposal the moment a date, price or venue moves.

3

A person decides, then you hear about it

No machine writes to the catalogue on its own. A change reaches your list once an editor has cleared it — which is why every field can tell you its source and the day it was last checked.

A score that shows its work

You never get a number without a reason. Every part of a score is a row you can open — and every weight behind it is a setting in the admin, not a constant compiled into the product.

Default profile
What the ranking is actually made of
Topic fit — how close the industries, topics and roles are to your profile0.45
Location — distance from you; online events count too0.15
Timing — far enough away to plan, close enough to matter0.10
Popularity — how much attention the edition is getting0.10
Price — measured against the budget you set0.10
Weights live in the database — a super-admin retunes them without a deploy.
Alerts

When something moves, you hear it

A keynote cancels, a second CFP wave opens, the price goes up. The watcher catches it on its next pass, an editor clears it, and it lands in your inbox — not on LinkedIn a month later.

Freshness

Every record says when it was last checked

Fresh, ageing or stale is a field on the record, not a feeling. Anything that goes quiet for too long gets queued for another look automatically.

The fields we are opening first

These are the verticals the taxonomy already covers. They are names of fields, not a claim about how full any of them is today.

  • European Tech
  • Fintech
  • Payments (MPE)
  • Artificial Intelligence
  • Crypto & Digital Assets

Yours missing? Write it in the form below. A vertical here is a taxonomy entry plus its sources and its editor — opening one is configuration, not a release, so the queue is short.

Data somebody stands behind

Machines collect, editors decide. Every change to an agenda, a price or a venue passes a human before it changes your list. That is why we can tell you not just what is true, but since when and on whose word.

Provenance
Every field knows where it came from

Not the website in general — the exact page a date, a price or a venue was read from.

Freshness
And when it was last checked

A record carries the day somebody last confirmed it. Old data is allowed to be old; it is not allowed to look fresh.

Decision
And who let it through

No machine writes to the catalogue on its own. That holds today, while the database is being built, and it will hold when it is full.

Questions we get most

When do you launch?

Once the first verticals have enough vetted sources and an editor behind them — that is exactly what is happening now. Leave your address and you will hear from us the day it opens; the roadmap shows what is already done.

Where does the data come from?

Official event sites and their agendas, plus aggregators we have vetted. Every field carries its source and the date it was last verified — and you can see both.

Is this just another event calendar?

A calendar shows everything and leaves the judgement to you. ConfBeacon ranks, and tells you why a line sits where it sits.

What if my field isn't covered?

Tell us. A vertical here is a taxonomy entry plus its sources and its editor — opening one is configuration, not a release, so it does not wait for a deploy.

Do you sell my data to organisers?

No. Organisers cannot buy a better position, and they do not get to see what you looked at or decided.

Be there when the light goes on

One message, on the day the catalogue opens. No newsletter, no drip campaign, and nobody else gets your address.

One email about the launch. Unsubscribing is a reply. We never sell addresses.