How a setup works
How a setup works
1. Look at the kit
The kit source is public at github.com/aska-digital/protean-kit. Open-core version 1.6.0.
2. Discuss a setup
Talk to ASKA about running it in your environment with ongoing service.
3. Run it in your environment
Hands-on setup inside the client environment, sold with ongoing service.
Who it serves
Who it serves
For technical teams
Proteus runs on local models, hosted models, or a mix. Optional privacy helpers prepare text before it leaves your machine. Redact flags sensitive text for review. Gist suggests a topic hint. Title drafts a label. Each role keeps to its lane. The reviewer is separate from the builder.
For buyers
The kit is free under Apache-2.0. ASKA charges for hands-on setup and ongoing service inside your environment. Pricing is public: setup, deployment, and training at $9,300 USD one time, plus $540 USD per month for ongoing service. Scope limits are stated in writing.
Full pricing and terms on the Qatar page · What ASKA has shipped
What this does not do
What this does not do
- Still being built: the conversational setup agent and the one-command installer.
- Setup today needs comfort with a terminal and some manual steps. Copying generated files into place is manual for now.
- No income, savings, or performance outcome is promised. ASKA does not guarantee uptime, response times, savings, or model performance.
Available now: the open-source kit, templates, working rules, build checks, and the site generator. Still being built: the conversational setup agent and the one-command installer. Full status list.
An illustrative example
Illustrative example
An illustrative walkthrough, not a live deployment: a repair shop wants a booking page. The Director frames the page and the done-checks. The Researcher gathers opening hours, services, and prices. The Architect turns that into a build plan. The Designer lays out the page. The Builder writes the code. The Reviewer checks it against the plan before anything is called ready. The client sees what is ready and what is still uncertain.
Illustrative — shows how the roles hand work to each other, not a delivered result.
What makes that work
What makes that work
Each role passes actual work to the next — research, plan, design, code — not a claim that the work happened. A separate reviewer checks the result. The handoff includes what is finished and what is still uncertain.
The door is open
What have you been wanting to make?
Set up your team, or talk to ASKA about a setup in your environment.