Connect on the #general channel on the Kroxylicious Slack workspace.

Follow us on Bluesky, and share your Kroxylicious story.

Follow us on X, and share your Kroxylicious story.

Sometimes it's just easier to talk face-to-face. We have a meeting every month that's open to anyone to come along.

The date an time is advertised on the #general Slack channel.

Have you got a use case for a proxy? Tell us!

Kroxylicious might be the perfect fit, and we can help explain how.

And if not there's a great chance your use case can help shape the future direction of the project.

We take our public APIs seriously and review changes carefully to ensure they're supportable in the long run.

You can propose API changes by opening a propsal in the design repo.

Fix typos, improve clarity or write new content.

We use the "documentation" label on issues and PRs for things related to documentation

This is a big, and growing project. We know it can be hard to know where to start.

One way is to try fixing a simple issue. Look for the `good first issue` and `help wanted` label on issues.

Do you have a long-form Kroxylicious story to tell?

Maybe it's a tutorial, or a production experience.

You're welcome to share with the world by publishing it on our blog.

People (unlike crocodilians) often like to follow the herd. If you're using Kroxylicious, let people know so they're encouraged to give it a try. Adding your company or organization to our ADOPTERS.md file helps.