# Beevelop

> Beevelop is a factory for building products. It runs as a company's product factory for three months, extendable to six; the factory stays with the client.

A factory is the setup that produces products, not the product itself. Concretely, that is the repository layout, the CI gates, the agent pipeline, the test suites and the deployment path. It runs in the client's infrastructure, under their accounts, against their own cloud bill. Beevelop builds the first product through it, end to end. That product goes to production and takes real load.

The period is fixed at the start; it does not quietly become a retainer. Architecture, technical diligence and advice are things the factory does, not separate purchases. Two things are handed over: the running system, and the documented way of working that produced it. Both stay when the engagement ends.

Beevelop UG (haftungsbeschränkt) has its registered seat in Dobel, Germany. Maik Hummel is its Managing Director.

Beevelop refuses two things. There is no staff augmentation, ever; Beevelop is never a head to be rented. There is no fixed-scope waterfall; the scope of a first product is not knowable in advance.

The site refuses more, and each line is checkable against the files it serves:

- No analytics, no tag manager, no tracking pixel, no cookies, no consent banner.
- No contact form, no newsletter, no comments, no search, no user account.
- No third-party embed of any kind; the typefaces are served from this domain.
- No price, and no client or customer named on any page.

## The site is four surfaces

- [Beevelop](https://beevelop.com/): the statement, the answer line, the credentials ledger, the offer and its refusals, the two hurdles it calls internal, the one address, the two products, and one line pointing at the page where the site measures itself. Every ledger row links to a primary source.
- [Hive](https://beevelop.com/hive/): the technical debriefs. Each takes one subject through problem, approach and result, and nothing else.
- [Maik](https://beevelop.com/maik/): the record. Twelve years in production software, eight of them in conversational and voice AI. The chronology starts in 2014; awards and press follow.
- [Legal](https://beevelop.com/legal/): the two legal documents. It is reached from the footer; the header nav carries Hive and Maik.

## Two documents, German governing.

- [Impressum](https://beevelop.com/legal/impressum/): the legal notice under § 5 DDG. German and English; the German text binds.
- [Privacy](https://beevelop.com/legal/privacy/): what the site does with data, written against this build. German and English; the German text binds.

## Problem, approach, result.

- [Kickgeist debrief](https://beevelop.com/hive/kickgeist/): the first debrief. A tournament product has one deadline and it belongs to somebody else.
- [Docker images debrief](https://beevelop.com/hive/docker-images/): the second debrief. Public container images, published since 2015; a tag is not evidence.

## Every figure here is derived.

- [This site, measured](https://beevelop.com/hive/this-site/): the third document on Hive, and not a debrief. It holds the site's own constants: the lattice, the type scale, the contrast ratios and the bytes, each read at build time from the file that defines it. It is reached from one line on the homepage rather than from the Hive index.

## Two products, one shipped.

- [Kickgeist](https://kickgeist.com/): a social prediction game for the 2026 World Cup. It runs on iOS, Android and web, localised, with an MCP server for agents. Beevelop built it and operated it through the tournament.
- A planning surface, unnamed until launch: for people whose year does not fit a calendar. Months are columns and days are rows; the whole year is one matrix. It is pre-launch, and there is no public address to link yet.

## One address reaches Beevelop

- [maik@beevelop.com](mailto:maik@beevelop.com): the only address that reaches Beevelop. There is no form.
- The privacy policy names one further address. It is GitHub's rather than Beevelop's, and it is there because the GDPR requires a route to the party that holds the server logs.

## Optional

- [robots.txt](https://beevelop.com/robots.txt): the crawl rules. Every named AI crawler is allowed the whole site.
- [Sitemap](https://beevelop.com/sitemap-index.xml): the four surfaces and their five documents, generated at build.