What is not yet open, and what that means for you
No jobs can be submitted, no rates are published, and design-partner intake is closed. A plain list of what E31 Network does not yet offer, and what a team can usefully do in the meantime.
· 4 min read
IN SHORT
Three things are not yet open on E31 Network: job submission, published rates, and design-partner intake. Nothing has shipped. What a team can do now is read the design, decide which of its workloads can wait for a queue, and write down a job precisely enough that it could be submitted when submission opens.
A reader who has gone through the rest of this library knows how a job on E31 Network is designed to work. This article is the shorter and less comfortable companion: a list of what is not available, stated once and plainly, followed by what a team can usefully do while that remains true.
Nothing on this list is hedged. If something is not yet open, the program says so.
Jobs cannot be submitted
The five steps, submit, rent, run, output, release, describe the design. None of them can be exercised today. There is no way to submit a job, no compute is being held for anyone, and no meter has started. The illustrative requests on the examples page are illustrations of how the design would treat them, not records of jobs that ran.
This means a team with a job that needs to run in the near term should run it where it can run it today. The network is not an option yet, and the library does not pretend otherwise. A team that reads the life of a job and finds the model fits is reading about a future option, not a current one.
Rates are not published
The only pricing fact in the preview is the mechanism: compute is metered by the hour for the hours it is held, and the meter stops when the job finishes. There is no rate attached to that mechanism. There is no minimum, no discount, no credit, no tier, and no commitment term, because none of those exist in the design as published.
Rates are to be published when access opens. Until then, any number a reader attaches to the network is their own estimate, and the article on when the meter starts is the most detailed thing the program can say about cost.
Design-partner intake is not open
The program intends to work with a small number of teams who have heavy, bursty AI jobs, can describe a job precisely, can engage at the engineering level, and will run a job for real when the time comes. The design partners page describes that profile so a team can judge its own fit.
Intake is not open. There is no form on this site and no intake channel, and that is deliberate rather than an oversight. When intake opens, the site will say so. In the meantime, the design partners page is a description of who the program is looking for, not a door.
Where the capacity comes from
This one sits on the program's published list of unsolved problems rather than its list of things not yet open, but it belongs here because a careful reader will ask. The program has not published where the compute in the pool comes from. It has said it has not solved the question. No article in this library speculates about it.
What a team can do now
Three things, none of which require anything to be open.
The first is to sort your workloads. The test is whether a job can wait for a queue. Training, fine-tuning, retraining, batch inference, footage and image processing, dataset processing, simulation, rendering, synthetic data, evaluation, data transformation, and analytics are the kinds of work the network is designed for. Anything that must answer in the moment, a control loop, live perception for a moving machine, a safety function, an interactive assistant, stays on your own infrastructure and is outside the network's scope. The workloads page draws the line in detail, and the piece on the queue explains why the line sits there.
The second is to write one job down. Pick the job you would submit first and describe it in the four declarations: the work, the data, the request, the output. The article on what a job declares covers each one. This exercise is useful regardless of where the job eventually runs, and it is the single thing the program most wants a prospective design partner to be able to do.
The third is to read the unsolved list critically. If your job depends on moving a very large dataset, or on fair scheduling beside jobs of a different size, or on a retention policy, those are open questions, and your reading of them is exactly the kind of engagement the program is after. The piece on why the preview publishes before it ships explains why those questions are public.
Element 31 also builds Czar, a sealed appliance for teams that want AI compute in their own rack. A team whose work cannot wait for a queue, or who needs compute now rather than when the network opens, may find that Czar is the relevant product. The network is for the jobs that do not need to own compute, and it is not yet open for them.
Questions this raises
- When will submission open?
- The program has not published a date and this library does not invent one. The honest status is that E31 Network is a technical preview and nothing has shipped. The site will be updated when that changes.
- Is there any way to register interest in the meantime?
- No. There is no form and no intake channel on this site. Design-partner intake is not yet open, and the design partners page describes what the program is looking for so that a team can judge its own fit.
- Should I plan around the network for an upcoming job?
- Not yet. Nothing can be submitted, so a job you need run in the near term should run where you can run it today. What you can do is write that job down in the four declarations, which costs nothing and will be useful whether or not it ever runs here.
KEEP READING