Direct intake

Tell me what you are trying to solve.

Useful context includes your identity provider, directory authority, Linux estate, lifecycle goals, operational constraints, and the evidence your organization needs before enabling writes.

Technical briefing

Architecture fit, authority boundaries, security posture, topology, and rollout design.

Platform walkthrough

SCIM, SAML/OIDC, FreeIPA, Foreman, classrooms, remote access, observability, and database control.

Support or deployment

Provisioning failures, federation issues, directory mapping, Linux enforcement, or production-readiness questions.

Prefer email? [email protected]

Messages sent to this address are routed to the FreeSCIM operator.

Secure contact form

Send a message

No account is required. Messages are not stored by the website.

Include enough context to understand the request.0 / 5000
Keep secrets out of the message.

Do not submit passwords, API keys, bearer tokens, private keys, SAML assertions, session cookies, or unredacted internal logs.

What happens after submission

1. Validate

Cloudflare checks the request origin, required fields, size limits, timing, bot traps, and submission rate.

2. Deliver

A structured notification is sent from [email protected] with your address set as the reply destination.

3. Respond

The FreeSCIM operator receives the full context and can reply directly to the address you supplied.

Privacy and operational boundary

The website does not maintain a contact-message database. Cloudflare processes the submission to deliver the email, and only minimal delivery metadata is written to Worker logs. The message body, email address, and submitted form fields are not intentionally logged by the Worker.