How commissions work
We take on a limited number of terminal simulation and CLI interface projects at any given time. That includes training environments, branded CLI onboarding sequences, CTF tooling, hacker-styled product demos, and anything else that lives in a fake shell window.
Every project starts with the form at the bottom of this page. No email address, no phone number — that form is your single entry point. We read every submission and reply once we've had time to think about scope and fit.
The build process
1. Submit the brief
Fill out the form below with your project description, intended audience, and visual direction.
2. Scoping exchange
We clarify what commands should exist, what the fake filesystem looks like, visual style, and any platform constraints (web, embed, standalone, LMS).
3. Scripted prototype
You see a working terminal with core interactions and command responses — rough polish, full functionality. Review and request changes here.
4. Build & refinement
Polish, edge cases, brand integration, performance tuning. Iterative feedback loop until delivery-ready.
5. Delivery & docs
Fully built terminal shipped with documentation explaining how the simulated shell behaves, how to customize it, and integration steps.
What you'll need to brief us
To move from form submission to a real scoping conversation, have these details ready:
- Audience. Are these students, employees, customers, CTF competitors, conference attendees? Who sits down and types into this thing?
- Commands & tools. Which real tools should be mimicked (curl, nmap, grep, git, custom proprietary CLI)? Can we invent new commands, or do all of them need to feel like the real thing?
- Visual direction. Kali Linux dark green? Retro amber monochrome? Your brand colours? Custom ASCII art?
- Platform & constraints. Web embed (iframe-friendly), standalone site, LMS integration, desktop app, conference booth display? Any size or browser limits?
- Scope hints. Roughly how many commands? How deep does the fake filesystem go? Any branching logic or narrative threading?
Send your project
This is the only intake channel. Fill it out, hit submit, and we'll review and reply once we've had time to think about your project.
No email address or phone number provided. This form is the sole intake channel. Submissions are read and we reply once we've had time to evaluate fit and scope.
Questions
How long does a typical build take?
Depends on scope. A simple training terminal with 5–10 commands: 2–4 weeks. A complex CTF with branching logic, fake filesystem depth, and custom styling: 6–12 weeks. We discuss timeline during scoping.
Do you work with agencies or just direct clients?
Both. Agency partnerships are fine — just be clear about it in the brief. We handle scoping and delivery with whoever submits the form.
Can you mimic existing real command-line tools exactly?
Mostly yes. We can simulate curl, nmap, git, grep, and most standard Unix utilities with real-looking behaviour. Custom proprietary CLIs are fair game too — we'll need documentation of how they work. Some tools are too complex or system-dependent to fake perfectly; we'll flag those during scoping.
How is pricing determined?
Scope-based. The form asks for a budget range, which helps us know if your project is in our wheelhouse. Detailed pricing happens after scoping — we'll give you a flat quote once we understand the build and timeline.
Can I see examples of past terminal builds?
Check the Work section for case studies and live demos. Terminal projects are a core part of what we do.