Cribl App Hackathon Official Rules

1.1 Sponsor. The Cribl App Hackathon (the "Hackathon") is sponsored and administered by Cribl, Inc. ("Cribl", “Us”, “We”, or "Sponsor").

1.2 Acceptance. By submitting an entry, entrant (“you”, “your”) fully accepts and agrees to be bound by these terms and conditions and any other rules, guidelines or policies referenced herein by Us.

1.3 Modifications. We reserve the right to amend these terms and conditions with or without any prior notice or may at any time modify, suspend, or cancel the Hackathon with as much notice as practicable through the Hackathon channels.

2. Eligibility

2.1 General Eligibility.

Entrant must be at or above the age of majority in their jurisdiction of residence;
Employed by either (a) an organization that is a current Cribl customer, or (b) an organization that is a current Cribl partner;
Permitted by their employer's gift, ethics, and procurement policies to accept an award of the stated value and
Legally able to participate and to receive an award under all applicable laws.

2.2 Exclusions.

Employees, officers, directors and contractors of Cribl, and their immediate family and household members
Judges, organizers or reviewers of the Hackathon
Individuals residing in any jurisdiction where the Hackathon is prohibited or restricted by law, including any jurisdiction subject to applicable trade sanctions or export controls.

2.3 Participation.

Entries may be submitted by an individual or by a team of up to four (4) people.
No individual may appear on more than one team or submit more than one entry.
Each team entry must designate one member as captain at the time of submission. The captain is the sole point of contact for Sponsor and the sole recipient of any award on behalf of the entry. The captain may not be changed after the submission deadline.

3. Registration

3.1 Registration Form. All entrants must complete the Hackathon registration at https://event-sign-up-form-9d5df2.zapier.app/hackathon2026. Registration is required before submission.

3.2 Submission. An entry is complete only when, on or before 1:30 pm CDT on September 30, 2026, all of the following criteria are met:

The project source is pushed to a public repository under github.com/Cribl-Community.
That repository contains an Apache-2.0 LICENSE file.
That repository contains the packaged App as a versioned .tgz, committed or attached to a release.
That repository contains a README describing what the App does, how to install it, the Cribl APIs and any proxy hosts it uses, and any setup steps required.

3.3 Repository access. Entrants must request and receive access to the Cribl-Community GitHub organization. All submitted work must reside in a public repository within that organization.

4. Project Requirements

4.1 Qualification. The project must be a custom Cribl App: a web application that runs inside the Cribl UI on Cribl.Cloud and is packaged and installable per Cribl's published Apps documentation. Packs, scripts, dashboards, prototypes, mockups, and presentations do not qualify.

4.2 Functionality. The App must install cleanly from the submitted package into a Cribl.Cloud workspace without manual patching, and must run without credentials not supplied by the entrant or otherwise available to Sponsor.

4.3 Use of the platform. The App must make meaningful use of at least one of: a documented Cribl API, the KV store, a backend function or a declared proxy host.

4.4 Prerequisites. Entrants are responsible for their own Cribl.Cloud access and for holding Workspace Administrator in the workspace where they build.

4.5 Data and secrets. Submissions must not contain real customer data, personally identifiable information, production hostnames, or live credentials. Any secret stored in the KV store must use KV encryption. Plain-text credentials in KV will result in disqualification.

4.6 New and pre-existing work. Entrants may use an idea conceived before the build window. Work on the project must occur during the build window, which opens September 14, 2026. A project that existed in any form before September 14, 2026 is eligible only if it was materially extended during the build window and the README identifies what changed. A project that has previously won any other competition is not eligible.

4.7 Third-party code and AI tools. Publicly available frameworks, libraries, templates and AI coding tools may be used, provided that (a) all such tools and components are credited in the README, (b) any incorporated code is under a license compatible with Apache-2.0 redistribution, and (c) the entry is not substantially a reskin of an existing application or tool. Failure to disclose is grounds for disqualification.

4.8 Tracks. Based on the relationship between the captain's employer and Cribl, entries are assigned by Sponsor to either the Customer track or the Partner track. Entrants may state a track claim but do not select their own track. A team including members from both a customer and a partner organization will be assigned to the Partner track. Sponsor's track assignment is final.

5. Judging and Winner Selection

5.1 Judges. Entries will be evaluated by a panel selected by Sponsor (the "Judges").

5.2 Stage One: Eligibility review (pass/fail). Following the submission deadline, each entry will be reviewed on a pass/fail basis to determine whether it meets a baseline level of viability. An entry passes Stage One only if:

It was submitted complete and on time under Section 3.2;
The repository is public within the Cribl-Community organization and carries an Apache-2.0 license;
The App installs and runs in a Cribl.Cloud workspace;
The README, build disclosure and AI tool disclosure are present; and
The entry contains no real customer data, no personally identifiable information and no plain-text credentials.

Entries that do not pass Stage One are not eligible for any award and will not appear on the attendee ballot.

5.3 Stage Two: Scoring. Entries that pass Stage One are scored out of 100 points as follows:

Criterion	Points
Usefulness	25
Craft	25
Originality	15
Completeness	10
Attendee vote	25

5.4 Judging criteria.

Usefulness: the extent to which the App addresses a real problem for Cribl users.
Craft: the quality of the implementation, including user experience and appropriate use of Cribl APIs, the KV store, backend functions, and the proxy.
Originality: the extent to which the App does something the product does not already do, or combines existing capabilities in a new way.
Completeness: whether the App installs cleanly, is documented, and is ready to be shared with the community as submitted.

5.5 Attendee vote. Registered CriblCon attendees may vote for one entry using the CriblCon mobile application during the voting period announced through the Hackathon channels. Only entries that passed Stage One appear on the ballot. One vote per attendee. Within each track, the entry receiving the most votes receives the full 25 points and each other entry receives points in proportion to its share of that leading vote count. Raw vote totals will not be published.

5.6 Final determination. The Judges' determination of the winners is final and binding. Where the Judges' assessment and the attendee vote diverge, the combined score as described in Section 5.3 governs and the Judges' decision on its application is final.

5.7 Ties. In the event of a tie, the entry with the higher Usefulness score prevails. If still tied, the higher Craft score prevails. If still tied, the panel chair decides.

5.8 Insufficient entries. If a track receives fewer than three (3) entries that pass Stage One, Sponsor may in its discretion reallocate that track's awards, combine the tracks or decline to award. Sponsor may decline to make any award where no entry meets a reasonable standard of quality.

6. Prizes

6.1 Awards available. Five (5) awards are available, each issued in the form of a digital prepaid card, as follows:

First Place, Customer track — US$2,000
Runner-up, Customer track — US$750
First Place, Partner track — US$2,000
Runner-up, Partner track — US$750
Chaos Gremlin Wildcard (either track) — US$500

One award per entry. No entry may receive more than one award. Awards are issued to the entry’s captain on behalf of the entry, and any division of an award among team members is the sole responsibility of the entry.

6.2 Chaos Gremlin Wildcard. The Chaos Gremlin Wildcard is a discretionary award selected by the Judges and may be granted to an entry in either track, including an entry that does not otherwise place.

6.3 Taxes. All federal, state, local, and foreign taxes on an award are the sole responsibility of the recipient. Where the total value of awards to a recipient in a calendar year meets or exceeds the applicable IRS reporting threshold, the recipient must complete and return a Form W-9 before the award is issued, and Sponsor will issue a Form 1099-MISC. For prizes awarded after December 31, 2025, that threshold is $2,000, so an award of $1,999 or less does not require collection of a taxpayer identification number. Award value is taxable income to the recipient whether or not a form is issued. Non-U.S. recipients may be subject to withholding and additional documentation.

6.4 Notification and claim. Potential winners will be notified at CriblCon and by email to the captain. A potential winner who cannot be reached, who does not respond within 30 days, who declines, or who is found ineligible forfeits the award, and Sponsor may select an alternate or decline to award.

7. Intellectual Property

7.1 Ownership. Entrants retain all ownership and intellectual property rights in their submitted projects and any underlying code, designs, or content created during the Hackathon. Nothing in these terms and conditions shall transfer ownership to Sponsor.

7.2 Required license. As a condition of entry, each submission must be published in a public repository within the Cribl-Community GitHub organization under the Apache License, Version 2.0. Entrants represent that they have the right to license all submitted material under that license.

7.3 License to Sponsor. By entering the Hackathon, each entrant grants Sponsor a non-exclusive, worldwide, royalty-free, perpetual license to install, run, reproduce, adapt, display, record, and publicly distribute the submission and its name, in whole or in part, for the purpose of judging, demonstrating, and promoting the Hackathon, Cribl Apps, and the Cribl community, including in blog posts, event content, social media, documentation, and the Cribl Marketplace.

7.4 Marketplace. Publication to the Cribl Marketplace is not automatic, is not a condition of winning and remains subject to Cribl's normal review process.

8. Warranties; Limitation of Liability

8.1 Warranties. Each entrant represents that the submission is their own original work except as disclosed under Section 4.7, does not infringe any third-party right, contains no malicious code, and complies with Section 4.5.

8.2 Disclaimer. THE HACKATHON, ALL MATERIALS AND ALL PRIZES ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

8.3 Limitation of Liability. In no event will Sponsor or its affiliates, or their respective officers, directors, employees, agents, or contractors, be liable to any entrant for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, goodwill, or business opportunities, arising out of or relating to the Hackathon, an entrant’s participation or inability to participate, any submission, any award, or these terms and conditions, whether based in contract, tort (including negligence), strict liability, or any other theory, and whether or not Sponsor has been advised of the possibility of such damages. By entering, each entrant agrees to release and hold harmless Sponsor and its affiliates from any and all claims, liability, and damages arising out of participation in the Hackathon or the acceptance, use, or misuse of any award.

9. Code of Conduct

9.1 Code of Conduct. All participants must comply with the Cribl Community Code of Conduct and with CriblCon event policies, in the Hackathon channel, at office hours, in submitted materials and at the event.

9.2 Prohibited conduct. The following are grounds for disqualification:

Submitting work created by another person and representing it as the entrant's own.
Misrepresenting the work performed, the team composition or the build timeline.
Exceeding the team size limit or entering more than once.
Using code created outside the build window without disclosure under Section 4.6.
Including real customer data, personally identifiable information, or plain-text credentials.
Tampering with the voting process, including coordinated vote manipulation.
Harassing or abusive behavior toward participants, staff, judges or attendees.

9.3 Process. Reports may be made to cbreshears@cribl.io. Sponsor will first review publicly available materials, including the repository and submission. If the matter is not resolved, Sponsor will inform the entrant of what has been reported and give them an opportunity to respond before any decision. Possible outcomes include a warning, removal from the ballot, disqualification, and forfeiture of any award.

9.4 Sponsor discretion. Sponsor may disqualify any entrant who, in its reasonable judgment, violates these terms and conditions or acts in a manner that undermines the fairness or integrity of the Hackathon.

10. General

10.1 Entire Agreement. These Terms and Conditions, together with any documents referenced herein, constitute the entire agreement between you and the Sponsor regarding the Hackathon.

10.2 Privacy. Personal information collected through registration and submission is handled in accordance with the Cribl Privacy Policy and used to administer the Hackathon, verify eligibility, contact entrants and issue awards.

10.3 Publicity. Except where prohibited by law, entry constitutes consent for Sponsor to use an entrant's name, employer, likeness and submission in connection with the Hackathon without further compensation.

10.4 Severability. If any provision of these terms and conditions is held invalid or unenforceable, the remaining provisions remain in full force.

10.5 Not an endorsement. Participation does not create any partnership, employment, or agency relationship, and does not constitute endorsement by Sponsor of any entrant or their employer.

10.6 Interpretation. Sponsor's interpretation of these terms and conditions is final. Rules questions should be directed to cbreshears@cribl.io or the Hackathon channel, and answers to material questions will be posted publicly so that all entrants receive the same information.