Code Management Exhibitor List

An exhibitor list for Code Management is a record of the companies taking space at the event — not the visitor badge list, not the conference programme, and not a speaker roster. Those are separate documents, and conflating them is the most common way teams misread a show like this one. For the 2026 edition the verified research is unusually thin: the event name is recorded, while the city, country, venue, organiser, website, dates and both exhibitor and attendee counts are blank. The register itself, its size and its sector mix are therefore unconfirmed at the time of writing. What the exhibitor data can still do is give shape to the search: it should be queried for the companies occupying floor space, the sectors they tag themselves with, and the geography their head offices sit in. Where a field is empty in the source, treat it as a question for the organiser rather than as evidence of absence. A missing stand number is not proof that a company is absent; it usually means the directory has not been refreshed.

• Exhibitor list covers companies with floor space, not visitors
• Visitor, speaker and exhibitor records are three different documents
• City, venue, dates and organiser remain unconfirmed in this research
• An empty field is a gap in the source, not proof of absence
• Reconcile roster size against the official Code Management directory

Nothing in the research classifies Code Management by industry, so the categories below are read from the event's name rather than from a confirmed sector tag. Treat them as search terms for the exhibitor list, not as a published roster. A show built around code management tends to draw companies selling version control and repository hosting, code review and pull-request tooling, static analysis and source-code security scanning, artefact and package repositories, dependency and licence management, developer portals and internal developer platforms, and the CI/CD layers that touch a repository. Around those sit the service businesses: consultancies that migrate engineering teams between systems, integrators who wire repositories into build and release pipelines, and training providers. Once the exhibitor directory for the 2026 edition is live, test these categories against the actual sector tags printed in it. Where the roster contradicts the expectation — if cloud or infrastructure vendors dominate, for instance — the roster wins. The exhibitor data is the evidence; the event name is only a hypothesis.

• Categories here are inferred from the name, not from a confirmed industry tag
• Watch for version control, repository hosting and code review vendors
• Static analysis and source-code security are plausible adjacent categories
• Artefact, package and dependency management vendors may cluster together
• Migration consultancies and CI/CD integrators form a second layer
• Let the published sector tags overrule any inference made here

Code management sits underneath every engineering organisation, which is why the tooling around it is bought slowly, by few people, and rarely replaced. A repository platform decision touches security, compliance, build infrastructure and developer experience at once, and the evaluation group is small: platform leads, developer productivity teams, security architects and the infrastructure owners who run pipelines. That buying shape is exactly why an event of this kind matters as a meeting point. It compresses vendors, integrators and the practitioners who live in the tooling into one floor, at one time, in one place. For anyone working from exhibitor data, the value is concentration rather than novelty: the exhibitor list becomes a map of which suppliers are investing in presence, and presence is a rough proxy for where those suppliers think the migration and consolidation cycles are heading. The caveat is that this research records no exhibitor or attendee count for Code Management, so how large that concentration actually is cannot be stated. Treat scale as an open question until the organiser publishes it.

• Repository decisions involve security, compliance, build and developer experience
• Evaluation groups are small and decisions are slow to reverse
• Exhibitor presence is a rough proxy for vendor investment, not a guarantee
• No exhibitor or attendee count is confirmed for this edition
• Scale should be verified with the organiser before it is quoted

The research records no city for Code Management, so no claim about its region, its host market or its catchment can honestly be made here. That is an unusual starting point for a page about exhibitor data, and it changes how the list should be used. Two different geographies are usually at play at any trade show: where the event is held, and where the exhibiting companies are headquartered. The venue drives who can attend on the day; the head-office field in the exhibitor list drives which markets the vendor community actually serves. Only the second of those is knowable from exhibitor data, and only once the directory is published. Until a venue is confirmed, resist the temptation to import assumptions from other developer-tooling events in other cities. When the location is confirmed, the practical move is to re-run the exhibitor list filtered by company origin and compare it with the host market, because a mismatch between the two tells you whether the show is a local sales floor or an international vendor showcase.

• No city or country is recorded, so no regional claim can be made
• Separate the show's location from exhibitors' head-office locations
• Venue determines who can attend; head office shows who vendors serve
• Re-filter the exhibitor data by origin once a venue is confirmed
• Do not borrow regional assumptions from other developer events

Exhibitor data for a code management event gets used by more teams than the show-floor audience would suggest. Sales and account-based marketing teams read the list backwards, looking for the vendors whose customers overlap their own territory. Partnership and alliances teams look for integrators and consultancies that could carry their product into engineering organisations they cannot reach directly. Competitive intelligence analysts track which rivals take space, how large their presence is described, and whether they return in the following edition. Recruiters scan for companies scaling developer-tooling teams. Procurement and platform teams use the exhibitor list as a shortlist for evaluation meetings they would otherwise book over months. Event marketers study sector mix to judge whether the audience matches their pipeline. None of these uses requires an attendee list; all of them depend on the exhibitor records being accurate, current and clearly labelled as to edition. That last point is the one to police hardest, because a stale exhibitor list from an earlier year will silently mislead every one of these teams.

• Sales teams map vendors whose customer base overlaps their territory
• Partner teams hunt for integrators and migration consultancies
• Competitive analysts track presence and repeat participation
• Procurement teams use the list as an evaluation shortlist
• Every use depends on the edition being labelled correctly

The value of an exhibitor list is decided by how many real questions a single record can close. For Code Management, the questions a reader will bring are predictable: which company is on the floor, what it sells, where it is based, how to find its stand, and how to make contact before the doors open. Fields such as company name, sector or category tag, country or city of origin, stand reference and website are the usual anchors, but this research does not confirm which of those fields the Code Management directory will carry, so the schema should be checked rather than assumed. Two further questions are worth testing against the source: whether the record distinguishes first-time exhibitors from returning ones, and whether it distinguishes a parent brand from a product line exhibiting under its own name. Both distinctions change how a list is read. A record that cannot tell you whether a vendor is new to the show is a weaker signal than one that can.

• Check the actual schema rather than assuming field coverage
• Sector tags and country of origin drive most filtering
• Stand references matter for pre-booked meetings on site
• Test whether first-time and returning exhibitors are distinguished
• Parent brands and product lines may appear as separate records

Stand numbering is an administrative fact; sector clustering is a commercial one. At developer-tooling events, vendors with adjacent propositions often end up near each other, and the resulting neighbourhoods tell a reader something the alphabetised exhibitor list does not. Repository and version control vendors tend to anchor a zone, with code review, static analysis and dependency scanning around them, while CI/CD and infrastructure vendors form a second cluster and services firms sit wherever the organiser places them. This is a pattern worth looking for, not a rule to assume, and this research contains no floor plan for Code Management, so the clustering cannot be confirmed here. If a plan is published, use it as a second lens on the exhibitor data: overlay sector tags onto stand positions and see which categories the organiser has chosen to place beside each other. That overlay often reveals how the event positions itself — as a security show, a platform engineering show, or a pure developer tools show.

• Stand numbers are administrative; sector clusters are commercial
• Look for repository vendors anchoring a zone of adjacent tooling
• No floor plan is confirmed in this research
• Overlay sector tags onto stand positions if a plan appears
• Placement patterns hint at how the organiser positions the event

Several fields that normally arrive with an event are absent from this research: dates, venue, organiser, website, and both headline counts. None of that means the 2026 edition is cancelled or hypothetical — it means the details were not captured, and the responsible action is verification rather than inference. Start with the organiser, because organisers control the exhibitor directory and are the only source that can confirm a stand allocation. Second, check whether a published exhibitor list is tied to a specific edition; a list without a year is not usable for planning. Third, be wary of directories assembled by third parties that mirror a show's name without a confirmed relationship to it, particularly where stand numbers and contact details are present but unverifiable. Fourth, when contacting exhibitors ahead of the event, reference the edition explicitly, because vendors exhibiting at one year's code management event may skip the next. Every one of those checks is cheap, and each prevents a planning error that exhibitor data alone cannot catch.

• Missing details mean unverified, not cancelled
• The organiser is the authoritative source for stand allocations
• Reject any exhibitor list that is not tied to a specific edition
• Treat unattributed third-party mirrors of the show with caution
• Name the edition when approaching exhibitors in advance

Timing changes what a reader wants from the same list. Before the 2026 edition, the exhibitor data is a targeting document: which companies are exhibiting, which sectors they occupy, and which of them are worth a pre-booked meeting rather than an opportunistic walk past the stand. Priority should go to vendors whose category sits closest to an active internal project, and to any exhibitor whose origin suggests they do not sell in your market through other channels. During the event, the same list becomes a checklist and an annotation surface: stands visited, conversations had, follow-ups owed, and the gap between what a vendor's directory entry promised and what the stand actually presented. After the event, it becomes a comparison base for the next edition — who returned, who withdrew, and which categories expanded or thinned. That third use is the one most teams skip, and it is where the exhibitor data earns its keep, because movement between editions is a cleaner signal than any single year's roster.

• Pre-event, rank exhibitors against a live internal project
• Book meetings with vendors unlikely to reach you otherwise
• On site, annotate the list with visits and follow-ups owed
• Post-event, compare rosters across editions for movement
• Year-on-year change is a stronger signal than one roster alone

An exhibitor list is a directory, and it is worth being blunt about its limits. It will not tell you which visitors will attend Code Management, what their job titles are, or what budget they control — those belong to a registration list, which is a different product with different consent rules. It will not tell you whether an exhibitor's product works, how large their stand will be in practice, or whether they will return next year. It cannot tell you deal sizes, pipeline, or which vendors are gaining or losing ground in the code management market; only their presence is recorded, and presence is not performance. It also cannot rescue a decision that needs a demonstration — a repository migration, for example, is judged on tooling behaviour, not on a directory entry. The honest framing for anyone planning around Code Management is that the exhibitor data narrows a long list down to a short one, and everything after that shortlist requires a conversation, a trial, or a reference call.

• No attendee names, titles or budgets appear in exhibitor data
• Presence on the floor is not evidence of product quality
• Stand size in a directory may not match the physical stand
• Exhibitor data shortlists vendors; it does not evaluate them
• Demonstrations and reference calls sit outside the list entirely