Early on, we made the decision to build ArkOne in layers. Start with the core design workflow, make sure it works, then build outward from there.
That means being deliberate about what comes next. Not just adding features, but adding the right features in the right order. Here’s what’s on the drawing board and why.
Frictionless entry
Sign up, get access, apply a discount code, upgrade your plan. It all happens inside the platform, on your schedule, without waiting on us. The goal is full autonomy. If you want to try ArkOne at 2am on a Saturday, you shouldn’t need to email someone and wait for a response. Everything you need to get started should be available the moment you decide to hop on.
Export
A range design that lives only inside ArkOne isn’t that useful. People need to document what they’ve built, share it with stakeholders, hand it off to whoever is doing the deployment. PNG export is already live for visual diagrams. We’re now building PDF export, which produces a complete design document directly from what you’ve already put into the platform; the kind of spec sheet you used to have to write yourself. Clean, organized, and ready for handoff.
Collaboration as a default
Ranges aren’t solo projects. Instructors build with TAs. Teams iterate together. Program directors need to see what’s being designed without having to ask for screenshots. We’re building for teams from the start, not adding collaboration as an afterthought. That shapes how we think about permissions, visibility, and how designs move between contexts.
The foundation is in place. Now we build on it. Each of these priorities moves ArkOne closer to what we set out to create: a platform where the barrier to designing realistic cyber environments is skill and intent, not infrastructure. We’ll keep sharing as development progresses.
-The Black Ark Labs Team
If you’d like to learn more about ArkOne Early Access or join the waitlist for future licenses, visit blackarklabs.com/waitlist.