Contact

Talk to FreshContext.

Technical walkthroughs, architecture reviews, integration questions, and strategic conversations. Mail reaches a person, not a queue.

Addresses

hello@: General enquiries
immanuel@: Founder, direct
corpdev@: Strategic and partnership
security@: Vulnerability reports

hello@freshcontext.dev LinkedIn

What to ask about

Useful things to open with.

The fastest conversations start from something specific in the repository or the specification.

Building on it

How evaluate_context handles caller-provided context, what the Source Profiles do to a decay curve, and where the Core import boundary sits if you would rather not go through MCP.

Verifying it

How to check a verdict yourself with the offline verifiers, what the published key document contains, and what changes when a key is rotated. Method in VERIFYING.md.

Integration review

Where FreshContext would sit in an existing retrieval, agent or governance stack, and which of the deployment seams that implies. Start from the demo and the repository.

Strategic conversations

Licensing, partnership, and acquisition discussions go to corpdev@freshcontext.dev.

What this site does not do. There are no account flows, no billing, no hosted dashboard, and no authenticated product surface here. The public package is freshcontext-mcp@latest: evaluate_context plus 21 read-only reference adapters, with /v1/verify live for ledger-backed verdict verification. The REST evaluate API, SDK and control plane remain open surfaces.