Flux Build Contest: Ship Your Own App by 25 Oct

Decentralised cloud network Flux has opened a week-long build contest for developers, announcing on X on 19 October 2026 that the best apps deployed on its platform by the end of Sunday 25 October will win back their hosting costs. The campaign, tagged #FluxWeek43, runs from 13:00 UTC on Monday 19 October to 23:59 UTC on Sunday 25 October. For anyone in the UK, that means it opened at 14:00 BST, and because the clocks go back on 25 October, it closes at 23:59 GMT that night.

The offer is aimed squarely at builders. Flux wants people to ship their own work — an AI agent, a bot, an API or a website — packaged as their own Docker image, and it says the winners will be judged on what the apps do and how well they are made. All of the details below come from Flux’s post on X; TSN found no separate rules page, so there are no fuller terms to check against.

In brief

Flux’s #FluxWeek43 contest runs 13:00 UTC Mon 19 Oct to 23:59 UTC Sun 25 Oct (23:59 GMT in the UK, after the clocks go back).
Five winners each get three months of their app’s hosting paid back in FLUX, up to 300 FLUX, plus a feature on Flux’s channels.
Entries must be your own Docker image, deployed with #FluxWeek43 in the app description; one entry per ZelID, and no published full terms.

What counts as an entry

Flux’s post sets out a short list of rules. The app must be your own: “It has to be your own Docker image. One-click templates don’t count.” Flux gives an AI agent, a bot, an API and a website as examples of the kind of thing it wants to see.

That rules out the quickest route onto the network. Flux offers one-click templates for popular software, but a template deployment will not qualify here, so entrants need a containerised app they have built and published themselves. Judging, Flux says, is based on “what they do and how well they are made”, and winners are “picked by the team”.

There is also a fairness rule: “One entry per ZelID.” ZelID is the identity Flux uses to sign in and deploy apps, so each person or account gets a single shot.

How to enter, step by step

The post gives four conditions, and they translate into a simple checklist:

Build your own app and package it as a Docker image. A template from Flux’s marketplace does not count.
Deploy it on Flux during the campaign window, between 13:00 UTC on 19 October and 23:59 UTC on 25 October.
Put #FluxWeek43 in the app’s description when you deploy. Flux says this is how you enter.
Keep it running. In Flux’s words, “The app has to be registered while it runs and still be up when it ends.” An app that goes offline or lapses before the close may not qualify.

Newcomers who have not deployed on the network before can start with Flux’s own guide, Deploy Your First App on Flux, published on its blog on 13 October. That guide predates the campaign and does not mention it, but it covers the basic deployment process. Flux’s Deployment Academy also walks through registering an app, which asks for a ZelID and a Docker image name in the usual username/image:tag form.

What the winners get

Flux says there will be five winners. Each gets “3 months of your app’s hosting paid back in FLUX, up to 300 FLUX, plus a feature on our channels.” Results will be “announced within 3 days after the end”, which is the only timing Flux gives for the decision.

The prize is a hosting rebate paid in FLUX, the network’s own token, and the amount depends on what your app costs to host, capped at 300 FLUX per winner. FLUX is a cryptocurrency whose value goes up and down, so the prize has no fixed cash value. This is a developer contest, not an investment opportunity, and nothing here is investment advice.

Flux’s post leaves several practical questions open. It does not say who is eligible by country or age, who sits on the judging team, exactly how three months of hosting will be calculated, or how and when the FLUX will be paid out. Entrants with questions on those points will need to ask Flux directly.

Our read

This is a straightforward way for Flux to get real, self-built workloads onto its network, and the no-templates rule and “still be up when it ends” requirement are designed to reward working apps rather than quick sign-ups. For developers already experimenting with agents or small APIs, a week is tight but doable, and the reward is a hosting rebate rather than a cash prize. The open question is the missing small print: with only an X post to go on, entrants should keep their deployment live past 23:59 GMT on Sunday and watch Flux’s channels for the results within three days.

How we sourced this

All contest dates, rules and prize details come from Flux’s post on X, via @RunOnFlux (19 October 2026, 13:08 UTC), checked through the X API. TSN found no separate rules or terms page on Flux’s blog, Medium or docs.
Background links to Flux’s blog guide and Deployment Academy explain how deployment works in general; neither mentions the campaign.