Frequently Asked Questions

AvenBox is a private, portable AI control system built around local execution, trusted continuity, and explicit routing choices. It is designed to keep serious AI work under your control rather than defaulting to cloud systems you do not own.

No. AvenBox is a real working local AI, privacy, and orchestration prototype currently being shaped into a production-grade product. It is early and real — not a finished consumer platform.

Real now: the local AI backend, the privacy-first processing layer, the orchestration and agent core, and the desktop automation backend. Prototype now: voice assistant flows, browser and PC action flows, and the full interaction experience. Estimated / directional: current public pricing and the Q1 2027 launch target. Roadmap: finished hardware design, polished mobile app, full platform maturity, and consumer-grade reliability.

AvenBox is designed to be local-first. Core AI runs on the device itself. Outside services can be used as explicit, user-chosen paths — they are not the hidden default.

No. Local execution is part of the system, but the harder problem being solved is governance: where intelligence runs, what stays private, what can extend to trusted systems, and how those decisions stay under your control.

Privacy in AvenBox is an architectural decision, not a setting or a marketing claim. The system is designed around a trust boundary: what runs locally, what may extend to trusted environments, and what never leaves your control without your knowledge. Specific certification programs and formal security audits are part of the roadmap, not current claims.

AvenBox is local-first. Suitable tasks are intended to run on-device without a cloud connection. That said, the system is not designed for universal offline certainty in all scenarios — some workflows may involve explicit trusted extension paths when you choose them.

The €1 reservation is the current early-access mechanism. It records serious interest in one of the public reservation tracks. Paying the deposit does not lock final specifications, guarantee delivery timing, or mean the product is finished.

It is not a preorder for a finished product. It does not guarantee final pricing, final specifications, or a specific delivery date. The reservation exists at an early product stage and should be read as controlled early-access interest, not a purchase confirmation.

The current public target is Q1 2027. That timing is directional — it reflects the current development direction and is not a fixed delivery commitment.

The first audience is privacy-sensitive professionals whose work, files, and internal thinking should not casually route through cloud systems — and early adopter founders and operators who want real AI leverage without giving up control or dependence discipline.

Yes, that is part of the direction. Broader ecosystem depth, deeper workflow continuity, and wider compatibility are roadmap goals — aligned with the Q1 2027 production target. They are not current product claims.

Aven Studios was founded by Marko Vodopivec and Muhammad Elladan Abdulazeez. Marko directs product vision, hardware engineering, and the orchestration framework. Muhammad directs the trust architecture and security model. The company is founder-led and early-stage — building toward a Q1 2027 production target.

Running a local model is the first step, not the full problem. The harder challenge is governing the complete system: where intelligence runs, what can extend outward, and what rules apply when it does. AvenBox is being built as the control layer that handles those decisions — not just a box that runs a local model.

Contact is open for general questions, investor inquiries, and press. Email hello@avenstudios.com — handled directly by the founding team. No intake filters.