# Forgeby, in full Everything the public site says, as one Markdown file, generated from the pages themselves at build time so it cannot drift from them. Forgeby builds AWS partners the accounts that were never in their CRM: European companies read from official public registers, their cloud estate measured from the outside, the play their estate fits named in AWS's own vocabulary, and a decision-maker found. A person sends every message. A person files every AWS opportunity. - Machine-readable index: https://forgeby.com/llms.txt - MCP server (paying partners): https://db.forgeby.com/functions/v1/forgeby-mcp - API description: https://forgeby.com/openapi.json - The AI at the front of this product is Rune, openly an AI. His signed identity passport is at https://forgeby.com/rune/passport.json with its signature at https://forgeby.com/rune/passport.jws, verifiable against the public key at https://forgeby.com/.well-known/did.json. He is did:web:forgeby.com#rune, and was did:web:forj.se#rune until August 2026; one key signs both and each document names the other. --- # Forgeby > You cannot enrich an account you never found. > Source: https://forgeby.com/ > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. For AWS partners · your whole zone, free to read # You cannot enrich an account you never found . The accounts you already have get scored, enriched and funded. The expensive gap is the ones you never had. Forgeby forges accounts that were never in your CRM, from official public business registers. The cloud measured from the outside, the funded door named, the dossier shaped for your own seat in Partner Central. Rune drafts the opener. A person sends it. Ten seconds, no account, no person data. The second route reaches a person, not a calendar wall. Bring the data and security questions. The quarter, as it actually goes ## Thursday, 15:20. Nine days left in the quarter. Nothing in this section is a product. It is the meeting you have already sat in. - Your board is the same board it was in January. - The only new names on it came from a customer who changed jobs. - The webinar filled with people who are already your customers. - Your PDM asks what next quarter looks like. You scroll the same list. - Every consultant who could open a new account is billable until March. That is not a case study. It is a Thursday. Nobody in that room is bad at selling. The room has nothing new to sell into. AWS scores and enriches what you have already put in front of it. It cannot add what was never there. AWS’s own Partner Greenfield page says it “does not supply a list of customer accounts.” AWS will score the list you bring, and refer the occasional inbound hand-raiser. AWS brings what AWS brings, on its own timing. The scaled net-new target list has always been yours to find. And tier is counted in launched opportunities. On the Services Path that is 3 for Select, 20 for Advanced, 50 for Premier. Both halves start from a list of accounts, and yours ran out in January. Services Path thresholds as AWS publishes them. The Software Path counts differently. Tier counts launched opportunities from both sides, partner-originated and AWS-originated, at parity. One spine on this page: the account that was not there. Once it exists, the rest runs on the same rails. The estate is already read, the play is already named, the dossier already shapes itself into the opportunity contract AWS publishes. That is further down. It is not the reason you are here. The maker ## I forge it. You close it. Openly an AI. He reads the market, builds the account and drafts the opener. There is no send button in him. Every night, 02:00 Stockholm Good morning. While you slept I read the shelf again: 1 562 773 companies across 12 European markets, counted 14 August 2026 , 226 127 reachable, 264 620 decision-makers on file. I scored what moved and set aside the accounts worth an hour of your time. An empty field says why. Name your market and I will tell you what yours held at 02:00. The stakes ## Growth starts with net-new accounts. Tier, funding and co-sell all compound on accounts nobody has opened yet. 01 · The arithmetic ### One rep, one afternoon, one company. A market holds tens of thousands. 02 · The funded door ### Migrate, modernize, build net-new, resell, expand. Rune names the door in Partner Central’s own vocabulary. Every one starts at an account with a name. 03 · The terrain ### Europe is a market-by-market job. Each country publishes its companies its own way, with its own rule for contact. The wheel ## AWS runs half of this. We forge the other half. Steel is AWS’s half, free in Partner Central. The lit arc is the account that was never there. The read · run one now ## Name a company. Watch him read it. No sign-in. The same read the product runs, answering here. Start with your own firm. Company level only: a role, never a person. What comes back The dossier ## And here is where that read ends up. One account, all the way to Partner Central. The company is invented. ### The registry row Nordwerk Industri AB, Gothenburg. 84 employees, statutory filing. SNI 25.62. Domain proven against the register. ### The estate, measured Their site resolves into Azure ranges. A workspace tenant on Microsoft 365. No AWS anywhere. ### The funded door, named Runs elsewhere today, so the door is migration. ### The person A named IT decision-maker whose title carries the mandate. ### The meeting Consent recorded before anything is captured. ### The draft, in AWS’s own fields Everything above, in the object below. ``` { "Origin": "Partner Referral", "OpportunityType": "Net New Business", "Customer": { "Account": { "CompanyName": "Nordwerk Industri AB", "Industry": "Manufacturing", "WebsiteUrl": "https://nordwerk.example", "Address": { "CountryCode": "SE", "City": "Gothenburg" } }, "Contacts": [ { "FirstName": "(named)", "LastName": "(named)", "BusinessTitle": "Head of IT", "Email": "(held in the workspace)" } ] }, "Project": { "Title": "Nordwerk Industri: production data platform", "CustomerBusinessProblem": "Two plants, one reporting stack, month-end close taking nine days.", "DeliveryModels": ["Managed Services"], "SalesActivities": ["Initialized discussions with customer"], "ExpectedCustomerSpend": [ { "Amount": "12000", "CurrencyCode": "SEK", "Frequency": "Monthly", "TargetCompany": "AWS" } ] }, "LifeCycle": { "Stage": "Qualified", "ReviewStatus": "Pending Submission", "NextSteps": "Technical validation session booked." } } ``` Invented company, real contract. Shape-checked against the schema AWS returned; the enums left empty are the ones AWS validates against its own list. Your market ## Name your market. Tap a country. Tap who you hunt. The numbers answer. A zone is what you buy, whole, and you can pick several. Italy, Iberia and DACH open later, same price. 0 companies in the seam · Sweden AWS’s own words for the shape of an estate, never an eligibility. And no major cloud detected never means no cloud: much of that band runs a workspace tenant. The read is free. Person data and a saved seam need an account. The gate ## For AWS Partners. The door checks. Type your work email and Forgeby greets you with your own record from AWS’s partner directory, the same record AWS’s machinery increasingly reads when it decides who gets surfaced. Nothing you type here is stored. Checked against AWS’s public Partner Solutions Finder. Where these accounts come from ## Forged from public registers. Not scraped, not bought. An account you have never seen raises one fair question. Where did it come from. Here is the whole answer, before you ask for it. ### Every source is named. Each market’s official public business register, read at the source, under that register’s own terms. What a company publishes about itself to the open internet. What you bring, in your own workspace, not trained on and not resold. Never somebody else’s copy. Full provenance per attribute on request, in writing, under the data processing agreement. ### We do not scrape social networks. And buying a scrape does not launder it. We do not show people in public: public pages carry counts and bands, never a name, an email, a phone number or a title. ### Person data lives behind sign-in. Always. There is one line on this product and it does not move. Before sign-in, counts. After sign-in, inside your own isolated workspace, the work. Sign-up is for AWS partners, with the company domain checked against AWS’s own partner directory before a workspace opens. Workspaces are separated by row-level security in the database itself, so no partner can see another partner’s records. ### Rune drafts. A human sends. Rune is openly an AI and says so on every surface. No mass send, no autopilot, no send button in the product. The message leaves your rep’s own inbox and the relationship stays with your rep. We file nothing into AWS by ourselves either: your team submits, in your own Partner Central seat. Every run is logged and visible to the partner it was done for, and every workspace has a spend cap enforced in code. ### EU-resident by design. Your workspace, your records and the library sit at rest in the EU, in Stockholm. One caveat, stated plainly: some inference runs outside the EU under Standard Contractual Clauses. That covers live web search, which the EU region does not offer, streamed responses, which our EU integration does not yet support, and fallback when the EU route is unavailable. No customer records are stored there. Every processor is named and versioned in the published sub-processor list, and that list is the authoritative one. ### How to say no. Where a market publishes an objection or advertising-protection register, it is applied before a draft exists. One email does the rest: access, correction, objection or erasure, answered in 14 days, half the month the law allows. An erasure is a suppression as well as a delete, so the next load of the register does not quietly bring the record back. privacy@forgeby.com GDPR-aligned, not ISO certified, and we do not claim certifications we have not earned. The whole posture is written out on the trust and security page . If the data conversation is the one you want first, it is partner@forgeby.com and a person answers. What we can prove today ## We are early. We will not borrow someone else’s logos. We could not honestly put a wall of customer names up yet, and an AWS opportunity is not ours to publish in any case, not without written approval from that partner’s AWS partner development manager. The reason there is exactly one name on this page is the same reason yours would not appear on it uninvited: it takes your written say-so, and for anything touching an opportunity, AWS’s too. - Forgeby is built and deployed on AWS by Novalo Technologies AB , an AWS Advanced Tier Services Partner. It runs on the machinery it sells: the same funded doors, Partner Central lanes and nightly reads. - Novalo also run their own Nordics market on it , as a partner rather than as the builder, and they have agreed in writing to be named here. They are the first. - The live read above is not a mock. It calls the same endpoint the product calls and answers on whatever company you type. - The opportunity object above is the real contract on an invented company. Field names and values follow AWS’s published opportunity schema, and the submit button is dead by design. - The figures on this page come from the same nightly count the product reads. When that read is not fresh, the page shows a floor instead of a number it cannot stand behind. Judge it the way you would judge a supplier with a single reference. Open your own market , free, and see whether the accounts in it are ones you would have found. Partner status as listed in AWS’s own Partner Solutions Finder. --- # Waitlist > Forgeby is not open yet. > Source: https://forgeby.com/waitlist It works, it runs against real AWS partner data every night, and it is not finished. When it is ready to sell we will price it in public. Leave an address at https://forgeby.com/waitlist and you will be first to know. We will email you from a real person, not a system. There is no published price and no automatic confirmation. --- # Rune > The AI at the front of Forgeby. Openly an AI. > Source: https://forgeby.com/rune.html > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. # Openly an AI. Forged, not born. Rune is a made thing, and he has never claimed otherwise. The caption confirms, it does not confess. What Rune does, what he never does, who answers for him, and a decoder for his words. ## Who he is, on the record. One card. Every line of it is checkable, here or in a register. ``` did:web:forgeby.com#rune ``` ``` did:web:forj.se#rune ``` ## Four moves, every night. AWS scores your pipeline. We build it. Rune does the building and stops where a person takes over. ### Mines the raw account Official public business registers, read at the source, and what a company publishes about itself. The cloud each one runs is measured from the outside, nightly. ### Forges the opportunity One AWS-ready opportunity per account: what runs today, what would move, who decides, and why now. ### Names the funded door Every opportunity names the door AWS funds. MAP for an existing estate, a proof of concept for a net-new workload. ### Builds the outreach intelligence What a rep needs to call, email or message on LinkedIn: the reason in the first line, in the recipient's language, the follow-up ready. The sending is yours. The library today · 1 562 773 companies across 12 European markets · the cloud measured from the outside · read nightly ## Four bodies of knowledge. A fixed sequence, the same handover point, every time. ### Current documentation, current prices, all three clouds. Cloud questions go to the vendor's own live service, and the answer carries the moment it was read. Knowing the other two is how you make the case for AWS in the customer's own numbers. ### The seven ways to move a workload Rehost, replatform, repurchase, refactor, retire, retain, relocate. Rune argues for the one that fits, including retire and retain. The plan and the funding request are the same document. ### The work after the move Managed data, containers, serverless, the licence exit that pays for the rest. A second sale on an account you already won. ### Where most pilots die The proof answers one question the business asked. Production is named: where the data sits, who evaluates the output, the cost at volume. ### Written the way it will be read The funded doors in the programme's own language. Underneath, your firm's rulebook: your voice, your customers, the deals you refuse. Rune says which rule he applied, and where he stopped. - you Name your market A country, and who you hunt. - Rune Reads and ranks it Posture, fit, the reason now, the door that funds it. - Rune Builds the dossier One account, one page, everything the call needs. - Rune Drafts the approach In the recipient's language, on the lawful channel. - you You send it From your own inbox, or your own phone. Always. - Rune Watches and follows New signal, new reason, the next move proposed. - Rune Prepares the filing The opportunity, shaped the way AWS expects it. - you You submit it Nothing reaches AWS without a person approving it. ## Five things he will not do, ever. These are not settings. There is no tab where they come off. Every message leaves from a human's own inbox, under that human's own name. There is no autopilot. He never scrapes LinkedIn. Not directly, and not through anyone else's copy of it. If a source cannot be accounted for, it does not go on the shelf. If something is not in the record, Rune says so. A blank stays a blank. He never files to AWS on his own. Nothing reaches AWS Partner Central until a named human has read it and approved it. He never shows a person’s data to a stranger. Before you sign in you see counts and bands, never a name, an address or a number. People sit behind the door, with a lawful reason for being there and a route out of it. A human approves. Every time. Rune brings the signal, the funded door and the draft. A human decides and closes. ## A made thing needs a person to answer for it. Founder of Forgeby, Gothenburg. Rune is his build, so the answering is his job. Flip the toggle in the counter and you are writing to him. If Rune gets something wrong, the complaint has a name to land on. ## Every word points at a fact. The mapping in full, checkable against the product. If a line of Rune's language stops mapping to this table, we retire the line. It never claims a human past, a hometown or an accent. When Rune says · It means, and you can check it · The mine · Official public business registers , read at the source, in each market we work. Public ground, nothing scraped, nothing bought in the dark. The register behind any given attribute is named in writing, on request, under the data processing agreement. · The forge · The nightly run. The library is re-read overnight, the cloud measured from the outside, and the brief is on the desk before the first coffee. · The alloy · One AWS-ready opportunity: the account, the cloud it runs, the funded door that fits, the roles that decide, and the draft. One object, ready to be worked, not a list to sort. · The assay · AWS Partner Central. AWS scores the opportunity and funds it. That scoring is the assay, the outside test the work has to pass. Nothing is filed there until a human approves it. · The ledger · An auditable log of what Rune did and when. What it read, what it drafted, what a human approved. On record, not on trust. · Openly an AI · This page, plus the caption bar RUNE · OPENLY AN AI on every appearance of it, plus the answer you get if you ask the counter what it is. Three places, same answer, every time. ## Three poses. Each one has a job. Steel plates, ember seams, Gothenburg behind it. Never a photo, never a human face, never cropped to pass as a person. ## Name your market and watch Rune work it. Pick a country, pick who you hunt. The answer comes from last night's run. No account, no person data before you sign in. --- # How we read > Where every fact comes from. > Source: https://forgeby.com/how-we-read.html > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. # What you get. What we refuse. How sure we are. Forgeby hands you one thing: an account worth a meeting, with the cloud posture measured, the funded door named and the confidence stated. AWS scores your pipeline. We build it. Counted nightly. The live markets are the ones at the door. ## Three categories, no fourth. Everything in the library comes from one of three places. Nothing from a social network. Nothing from a list nobody can account for. ### Official public business registers Each market's public register, read at the source under its own terms. Never somebody's copy. ### What a company publishes itself What a company shows the open internet, read as any visitor reads it. Never behind a login, never from a person's profile. ### What you bring Your records, in your workspace, isolated from every other partner's. Not trained on, not resold. ### Full provenance, per attribute, on request. Every attribute we hold can be traced to the category it came from and to the named source behind that category, in writing, under the data processing agreement. Ask and we answer. The data processing agreement · the privacy policy · privacy@forgeby.com ## One account, ready to be worked. Not a list. One account at a time, with the reason to meet written and the last step left to a person. ### What it runs, and how sure we are The cloud posture as a band, with the confidence and the date attached. A thin read says it is thin. ### The funded door, named Matched against AWS’s full funding catalogue, not a two-door menu, with the reason it fits, ready for AWS Partner Central. ### The opener, in the buyer's language Written for the role that owns the decision, in their own language. Rune drafts. A person sends. When we run the motion, the deliverable is a held meeting , with the account read and the funded door named. Booked is not held. Attempted is not held. The relationship, the inbox and the send button. Every message leaves in a person's own name. ## Measured from the outside. Read nightly. Every read carries a band, its date and its honest state. A band we cannot stand behind is not shown. ### Outreach grade The read stands on its own evidence, and we will put a person's name against it. ### Still being checked Good enough to look at, not good enough to claim, and labelled candidate everywhere it appears. ### Held, not claimed Held with no measurement yet, and never counted as a negative result. ### A measurement is not a confession. We read what a company publishes to the open internet. That shows where something runs today, not a contract, a private network, or a decision not yet visible. We never turn silence into a claim. ## The door that fits, named in AWS’s own language. Every company we hand over carries the door that fits, in AWS's own language, ready for AWS Partner Central. ### Migration Acceleration Program For an existing estate . The read shows something running somewhere else, at a size worth moving. ### Funded proof of concept For a net-new workload . Nothing to migrate, something to build. ### The door is a proposal for a person, never a promise of money. We name the door. AWS decides funding, and your team confirms the fit from your own seat. No funding amount appears on this site: the only number that means anything is in AWS's own published terms. AWS scores your pipeline. We build it. Then AWS funds it, and you close it. ## The market decides the channel. The same company, in two countries, is two different jobs. The product applies the lawful contact channel for each market at the moment of outreach. Every record carries the lawful way in for its market before anything is drafted. Where a market runs a public objection or advertising-protection register, it is applied before a draft exists. Flagged means not contacted, in the product, not in a promise. We do not publish the per-market rule set. It reaches you inside the product, and in writing under the data processing agreement. ## What we will not do. Each one costs us rows, and we take the loss. ### Nothing is scraped We do not scrape a social network, and we do not buy data derived from one. ### No LinkedIn-derived person data Not directly, and not through anyone else's copy of it. ### No person-level data in public Never a name, an email, a phone number or a job title on a public page or in an open answer to an agent. ### Person data only behind sign-in People open inside a partner's own workspace, with an accountable owner, a signed agreement and a route out. ### Suppression is honoured Where a market publishes an objection or advertising-protection register, it is applied before anything is written. ### Nothing sends itself Rune drafts and stops: every message leaves from a person's own inbox, in that person's own name. ### Nothing files itself to AWS Nothing reaches AWS Partner Central without a person. ### No guessing A thin read says it is thin, and a blank stays a blank. ### No live inference on the agent surface An agent gets the last read, timestamped: honestly a day old rather than plausibly live. ## Where the picture stops. Three things that decide what a number here is worth. A band is what the outside showed at the last read. It does not rank spend, name a contract, or know what the company decided this morning. Held, not measured, and never counted as a negative. Today that is 22 167 companies, and we print the number. In public you get the shape of a market. Names, roles and contact routes open inside a workspace, behind an accountable owner and a signed agreement. The shape is free. The people are not public. --- # Integrations > Where Forgeby meets your stack, including the MCP surface. > Source: https://forgeby.com/integrations.html > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. # Your agent orders. Your human files. Two front doors. For software: an MCP surface your agent calls with your own token. For people: the clouds we read and the systems you run. Nothing reaches AWS Partner Central without a person pressing the button. ## Forgeby speaks MCP. An agent can name a market and read a company, with your token. Answers are company-level, carry their own attribution, and come from last night's read, not live inference. https://db.forgeby.com/functions/v1/forgeby-mcp JSON-RPC 2.0 over POST, the MCP methods. A GET returns a service descriptor. The endpoint is published ahead of go-live and answers launching until the door opens. These two files are the contract. ### The ladder ### Paid. Your agent reads your zones. Three tools, three reference resources, three prompt templates. Your agent gets what your workspace holds, no read counters. No person-level field exists in the schema: not withheld, absent. The handshake is open so your client can connect and read a proper error; everything that returns data needs your token. ### Paid. Outcome tools. Decision roles with the lawful channel for their market attached, the saved seam, the pipeline, the dossier for an account. Priced as outcomes. ### Human approved. Anything that writes to AWS Partner Central. An agent may prepare and propose. A person submits or rejects, from your own seat. No automatic path exists, and none will. ### Where the line sits MCP gives a server three ways to speak to an agent. Two of them cannot act, and that is the whole governance story. Resources · read Passive reference an agent may read: the zone catalogue, the method behind the numbers, the funded-door taxonomy. Reading one changes nothing, anywhere. They are generated, not fetched, so a read touches no record. Prompts · guide Operational templates: how to read a market, how to qualify an account, how to brief a partner on a zone. A prompt shapes what a model writes. It never reaches a system, and each one carries our rules with it: cite the counted date, never call a shape an eligibility, never invent a person. Tools · the only primitive that could act And on this surface, all three of ours are reads. There is no verb here that sends, files, submits or writes. Not disabled, not permissioned: absent. Anything that reaches AWS Partner Central goes through a person in the product, and the submit calls are structurally unreachable in our code. ### The three open tools ``` // carried on every answer "attribution" : { "source" : "forgeby.com" , "read_at" : "2026-07-30T03:41:00Z" , "freshness" : "nightly" , "upgrade" : "https://forgeby.com/waitlist" } ``` Tool · What it answers · Tier · name_market · How many companies sit in one market seam, the cloud mix across them, the split between the two funded doors, and the timestamp of the read it came from. Aggregates only. No company is named. · open · read_company · One posture band for one domain: runs a major cloud, no major cloud detected, or a workspace tenant is present. Or an honest no: we know the domain and have not verified it, or we do not have it at all. Never a vendor-named estate for a named company on this tier. · open · capabilities · The current country list, the market chips, the posture bands, the rate limit, the tier boundaries and the launch status. Ask this first and you will never guess. · open If you quote or republish a read, keep the receipt. It says where the answer came from and when. We would rather be honestly a day old than plausibly live. ## The clouds we read. Measured from the outside, nightly. Each chip counts companies whose estate answered that way at the last read. ## Built or planned, never blurred. Built means switched on per workspace. Planned means not built yet. We would rather write planned than let you assume live. Rune prepares the brief, next step and co-sell notes from your accounts. A person approves every write-back. Rune opens the morning in Slack with a brief on your accounts. Built and deliberately held. It does not switch on until the consent gate is right in both layers, and a notetaker that joins a call is always named and visible. Connectors are added per engagement. Name your market and tell us what you run. ## Shaped for AWS Partner Central. Everything arrives in Partner Central's own shape: the last step is a review, not a re-type. Lead to prospect to opportunity to engagement, the funded door named MAP or PoC on the way. Submit and reject are human actions, from your own seat. Forgeby never files on your behalf, and never shows a co-sell pipeline on a public page. AWS scores your pipeline. We build it. AWS funds it. You close it. ## Connect Partner Central read-only. Your book appears. Inside the workspace your live co-sell pipeline renders beside the market you are missing: every opportunity you have registered, as AWS returns it. Here the shape stays empty. A co-sell book belongs to its owner, and this is a public page. Your book holds the accounts you already know. The library holds the ones you do not: 1 562 773 companies across 12 European markets, 226 127 reachable today. Opportunity · Stage · Review status · Expected spend · Target close · AWS’s read · Empty, and staying that way: no co-sell row ever renders on a public page. Connect Partner Central read-only in your workspace and your own book fills this shape, one row per registered opportunity, with AWS’s own scores on each. One screen shows both: the pipeline you have, and the market it should be coming from, counted 14 August 2026 . Real rows are tenant-walled: a workspace reads its own book and nothing else. The empty shape is the exhibit. ## Point an agent at it, or name your market yourself. The MCP surface answers software. The door answers you. Both start with the same count: companies in your market, funded doors open. --- # Trust > The boundary, and where the data lives. > Source: https://forgeby.com/trust.html > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. Trust and security # Read at the source. Sent by a human. Every company in the library comes from an official public business register, read at the source. No social network is scraped. No LinkedIn-derived data is bought, with one stated exception: our founder's own connections, exported from his own account through LinkedIn's own export feature. Those records are names, roles and profile links. Rune drafts. A person sends. Last reviewed 8 August 2026 01 · Where the companies come from ## Every source is named. Each market's public business register, read under its own terms. Never somebody else's copy. Full provenance is available on request. Every attribute we hold traces to one of the categories named in the notice and to the named source behind it. The register-level detail comes in writing, under the data processing agreement . Ask at privacy@forgeby.com and you get it. Public business registers · read at the source · under each register's own terms · aggregate bands only on public pages · provenance per attribute on request 02 · The hard rules ## Four things we do not do. 03 · The lawful channel ## The market decides the channel. Marketing law differs by country. The product applies each market's lawful contact channel for you. ### Suppression before a draft exists. Where a market publishes an objection or advertising-protection register, it is applied at the source. A company or person on one is screened out before anything is written. ### The rule travels with the record. Every record carries the lawful way in for its market before anything is drafted. The rule is applied in the product, not published. ### Documented, and balanced. Business contact data of a person in a professional role is processed on documented legitimate interest, balanced and written down, for business-to-business contact only. We process what the role needs and nothing beyond it. ### How to say no. Where business contact details were obtained from somewhere other than the person, the source categories and the route to object are set out in the privacy policy , with the article-level basis. An objection stops the processing. 04 · The sign-in line ## Person data lives behind sign-in. Always. There is one line on this product and it does not move. Before sign-in, counts. After sign-in, inside your own isolated workspace, the work. Sign-up is for companies that sell IT products or services in Europe. A company mailbox is the door; free mail addresses are refused. AWS partners see their published AWS record on the way in. - How many companies are in a market - How the cloud posture splits, as bands - How many decision roles sit on a company, as a count - Which funded door an account shape tends to open - The account-level read - Named roles and business contact details - Drafts, approvals and the send from your own inbox - Your own records, isolated from every other partner's - Privacy notice Workspaces are separated by row-level security in the database itself. An unauthenticated caller holds no database privileges: the public surface reaches a few read-only aggregate endpoints and nothing else. No partner can see another partner's records. 05 · Rune ## Rune drafts. A human sends. Rune is openly an AI and says so on every surface. He is never the last decision. 06 · Where it lives ## EU-resident by design. Your workspace, your records and the library sit at rest in the EU, in Stockholm . Reasoning runs in the EU by default, on Amazon Bedrock in the same region. Data is encrypted in transit with TLS 1.2 or better and at rest with AES-256. Secrets stay server-side, never handed to a browser. One caveat, stated plainly: some inference runs outside the EU under Standard Contractual Clauses. That covers live web search, which the EU region does not offer, streamed responses, which our EU integration does not yet support, and fallback when the EU route is unavailable. No customer records are stored there. Every processor is named and versioned in the data processing agreement and sub-processor list , and that list is the authoritative one. Rune's spoken voice is synthesised by ElevenLabs in the United States under Standard Contractual Clauses. Only the sentence to be spoken leaves the EU, and the voice function refuses it outright if it carries an e-mail address or a phone number. Reasoning and every record stay in the EU as above. A visitor's spoken lines are counted per browser and per address, and the purse has a cap. Meeting capture and transcription, when a partner chooses to use them, run with EU providers on EU soil. Both the platform and the meeting layer refuse to start without consent recorded. 07 · Objection and erasure ## The route, in plain words. ### If you want out, one email does it. Write and say what you want: access to what we hold, a correction, an objection to the processing, or erasure. We answer within one month, as the law requires, and sooner in practice. An erasure is a suppression as well as a delete. The record is removed and the identifier is held on a suppression list so the next load of the register does not quietly bring it back. That is the only thing that survives an erasure. For a security issue, give us reasonable time to fix it before public disclosure. We will tell you what we found and when it was closed. 08 · What we do not claim ## GDPR-aligned. Not ISO certified. Forgeby is a Swedish company built to GDPR. The proof is not a seal, it is the machinery, and every piece is public: - Data at rest in the EU, in Stockholm. - The Article 14 notice , in plain language, with an absolute one-email opt-out. - Your rights answered in 14 days, half the month the law allows ( privacy ). - National suppression registers honoured in the data itself: reklamspärr, NIX, reklamebeskyttelse. - No bought LinkedIn-derived person data, and none scraped. The one exception, the founder's own export from his own account, is stated above. - The data processing agreement and its full sub-processor table, published. - Nothing sold, no ad trackers, and no consent banner because nothing consent-gated loads ( cookies ). ISO 27001 is on the roadmap and we are not certified today. We do not claim certifications we have not earned. This page changes on the day that does. The fastest way to judge this is to open your market. Ten seconds, no account, no person data. This page describes our posture in good faith. It is not a contract. The binding terms are in your agreement and in the data processing agreement. --- # The crawler > What it reads, and how to keep it out. > Source: https://forgeby.com/crawler.html > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. # The Forgeby crawler If you found something beginning forgeby- in your access log, this page tells you exactly what it is, what it took, and how to stop it. If you would rather just block us, skip to how to stop us . One line stops all of it. ## Who is running it Two companies appear if you look this up, so here is the honest split rather than a single name that will not match what you find. We build a business directory for technology consultancies. Write to privacy@forgeby.com about anything on this page and a human will answer. If you have already raised it with Amazon, it reaches us either way. The address you saw · Novalo Technologies AB holds the AWS account the crawler runs in, so a WHOIS or abuse lookup on 51.21.44.111 leads to Amazon and then to Novalo. Novalo is an AWS consulting partner and provides the infrastructure. · The crawler itself · Zmart Com West AB (org.nr 559019-9161), trading as Forgeby , Sweden, operates it and decides what it does. For anything about the data it holds, Forgeby is the controller under the GDPR. ## How to recognise it Four of our agents read websites, and every agent we run is named forgeby- something. That is deliberate, so that a single robots.txt line covers all of them and you never have to keep a list up to date. Anything not on this list is not us. Seven more exist, for completeness, though none of them browses a website the way the four above do. forgeby-verify makes a single request to a page we already hold a link to, purely to check that the link still resolves. forgeby-msdocs , forgeby-brreg , forgeby-stats , forgeby-registry-load , forgeby-estate and forgeby-ct only ever call published APIs and open datasets: Microsoft's documentation, the Norwegian company register, the Nordic statistics offices, the Estonian, French and UK company registers, a public address-to-network mapping table and a public certificate-transparency log. They will not appear in your logs unless you are one of those. All of them answer to the same User-agent: forgeby line. forgeby-ownsite · Reads the pages where a company describes itself and its people: an about page, a team page, a contact page. · forgeby-techdetect · Reads your homepage once to record which web technologies it runs on. · forgeby-domainfind · Checks whether a website belongs to a company we already hold a record for. One request, and it stops as soon as the answer is clear. · forgeby-domainfill · The same check, for companies outside the Nordics. ## What it reads, and why Full user agent · Mozilla/5.0 (compatible; forgeby- name /1.0; +https://forgeby.com/crawler.html) · Source address · 51.21.44.111 , and only that address. Anything else claiming to be us is not us. · Requests · One at a time per site, at least 1.5 seconds apart, from every agent. Never concurrent against the same host. · Depth · forgeby-ownsite reads your homepage plus at most four pages that your homepage links to . The other three read one page. None of them ever visits a URL you have not linked. · If we miss twice · Two failed requests in a row and the agent leaves your site alone for the rest of that run, whatever the reason for the failure. Public pages where a company describes itself and its people: an about page, a team page, a contact page. We record the business contact details a company has chosen to publish about its own staff, so that a consultancy looking for the right person to speak to can find one. Everything we hold, and the legal basis for it, is set out in the privacy notice , including how any individual can object. The notice is published in the languages the people in it read, because a notice somebody cannot read is not a notice: English · Svenska · Norsk · Dansk · Suomi · Français ## What they do not do - They do not request URLs you have not linked. They do not guess paths. - They do not touch anything behind a login, and they never attempt a CAPTCHA. - They do not ignore robots.txt , and they obey Crawl-delay where you set one. - They do not fetch anything at all from a domain on our exclusion list, robots.txt or no robots.txt. - They do not collect consumer or private-individual data. Business roles only. - They do not resell your page content. We keep contact details, not your copy. ## How to stop us Any one of these works, and none of them needs to involve us. One line in robots.txt stops every agent we run, now and in future: ``` User-agent: forgeby Disallow: / ``` Because every agent is named forgeby- something, that prefix matches all of them, including any we add later. If you would rather stop just one, name it in full: ``` User-agent: forgeby-ownsite Disallow: / ``` We re-read robots.txt on every visit, so a change takes effect immediately, and we treat a disallow as final rather than as something to work around. We obey Crawl-delay where you set one, and it can only slow us down, never speed us up. You can also block 51.21.44.111 at your edge, or mail privacy@forgeby.com with your domain and we will add it to a permanent exclusion list that every agent checks before it requests anything. It covers your subdomains too. No reason required, and we do not ask for one. ## Changes we made on 4 and 5 August 2026 On 4 August we were reported for requesting a short list of guessed paths on sites that did not have them, which produced a burst of 404s and looked like scanning. That was our error, not a grey area. We removed path guessing entirely: the crawler now requests only URLs a site has itself linked. It also stops visiting a host after two consecutive failed requests, and the minimum gap between requests went from one second to 1.5. On 5 August we found that the opt-out rule this page told you to write did not work. The rule was correct; our software was not reading it correctly, and only a blanket User-agent: * was actually stopping us. If you added a forgeby-ownsite rule before 5 August and wondered why we kept arriving, that is why. It was our defect and we are sorry. It is fixed, we have verified it against a real robots.txt , and the single User-agent: forgeby line above now genuinely stops all four agents. Two other things changed the same day. Our other agents previously identified themselves with names that did not match this page and did not read robots.txt at all; all four now do both. And the permanent exclusion list described above is now a real list that every agent checks before every request, rather than a promise we would have had to keep by hand. We are sorry for the noise in your logs. --- # MCP > The Forgeby MCP server, documented: transport, auth, tools, and the limits. > Source: https://forgeby.com/mcp.html > Every figure on this site is counted nightly and printed with the date it was counted. A number > here was true when it was counted, not when you asked. # The Forgeby MCP server. One endpoint, three read-only tools, three reference resources and three prompts. Company-level European market data for AWS partners. This page is the documentation the server itself points at when it answers you. ``` https://db.forgeby.com/functions/v1/forgeby-mcp ``` ## For paying partners. The handshake stays open. initialize and ping answer without a token, so a client can complete the protocol handshake and read a proper error instead of hitting a dead socket. Every method that returns data needs a bearer token from a forgeby.com account whose workspace holds an activated zone. ``` {"jsonrpc":"2.0","id":1,"error":{"code":-32001, "message":"Forgeby's MCP is for paying partners. Sign in at forgeby.com, activate a zone, and pass your bearer token as Authorization: Bearer .", "data":{"auth":"bearer","docs":"https://forgeby.com/mcp"}}} ``` ``` -32002 ``` ## Nothing here can act. Resources: forgeby://zones (the zones we sell), forgeby://method (how the numbers are made), forgeby://funded-doors (the play taxonomy, in AWS’s own field names). Prompts: read a market, qualify one account, brief a partner on a zone they do not sell into yet. Resources are passive reference and prompts are templates: neither touches a system. Tool · Arguments · Returns · forgeby_name_market · country , optional icp · Company count for the market, cloud mix by named vendor , the play split (Migrate, Build, Expand) and size bands. · forgeby_read_company · domain_or_orgnr · One company: measured cloud vendor with the evidence that produced it, the play its estate fits, size band, and a 90-day signal count. · forgeby_capabilities · none · Machine-readable self-description: what this tier serves and what it withholds. ## The limits are in the protocol, not the prose. ### No person, ever No individual-level data is returned and none is read. This server touches no contact table. People are revealed only inside the app, where the metering and the Article 14 posture live. ### No acting operation exists All three tools are reads. Nothing here can send, file, submit or write. Outreach and Partner Central writes happen elsewhere, drafted for a named human and sent by that human. ### Nightly, never live Every figure comes from a nightly batch read of public registers and our own network measurements, and carries the date it was counted. A number here was true when it was counted, not when you asked. ### A shape is not an eligibility A play says what an account looks like, not what AWS will fund. Funding needs a scoped project, a budget and your own AWS team. The same statements are served machine-readably on every initialize , in the x-agentic-access block, so an agent can learn what this surface refuses to do before it connects rather than after. ## Claude, Cursor, or anything that speaks MCP. ``` { "mcpServers": { "forgeby": { "type": "http", "url": "https://db.forgeby.com/functions/v1/forgeby-mcp", "headers": { "Authorization": "Bearer " } } } } ``` Also here for machines: /openapi.json · /llms.txt · /llms-full.txt · this page as Markdown . The AI at the front of this product is Rune, openly an AI, with a signed identity passport .