In progress / Tenqora Agent / Amsterdam · Düsseldorf
Personal AIassistants.Built around you.
A persistent workspace for your projects, tools and AI assistants — on dedicated infrastructure you can control.
We are developing the environment behind a personal assistant: dedicated Mac workspaces, project context, task history and secure access from the browser. The project brings infrastructure and day-to-day work together across Amsterdam and Düsseldorf.
AMSTERDAM / DÜSSELDORF
- Project
- Personal assistants · Tenqora Agent
- Locations
- Amsterdam & Düsseldorf
- Stage
- In progress · Controlled pilot
THE IDEA
Your work continues.
Your context stays.
A personal assistant needs more than a conversation. It needs a working environment, access to the right project and a clear record of what has happened. That is the foundation we are building.
A Mac for your work.
A dedicated physical Mac workspace provides the environment for development tools and applications. The controlled pilot covers provisioning, access, return and reissue of the original test machines.
Work organised by project.
Projects, tasks and activity history stay together in a tenant workspace. The aim is to let an assistant continue a defined piece of work with the context and tools it is allowed to use.
One place to follow progress.
The web dashboard brings projects, task operations and environment observations into one view. It is designed for desktop and mobile access, with a separate native mobile experience still in development.
Visible work, traceable results.
Persistent task operations and activity records form the execution foundation. Provider-backed AI execution is a development track, distinct from the platform’s existing task-management capabilities.
Add what the project needs.
Storage, archives, Kubernetes environments and repository workflows are separate options. They can be developed and qualified independently, without making every workspace depend on every service.
Observe the environment.
Tenant-scoped environment and application checks provide a view of the resources a customer is allowed to see. Operators manage the underlying fleet through a separate access boundary.
INTENDED ASSISTANT WORKFLOW
From an instruction
to a reviewed result.
The target is a continuous working loop: define the task, use the permitted tools, follow execution and review the result. Work remains tied to a project and its access rules.
Define the work.
Select a project, describe the outcome and make the required context available. Keep the scope and permissions explicit.
Use the workspace.
The assistant works through the project’s authorised environment and integrations, with a dedicated place for tools and files.
Follow the task.
Review activity and execution status. A request being accepted is different from the work being completed.
Review and continue.
Inspect the result before consequential actions, retain the project history and continue with the next task.
This is the assistant workflow being developed. The current pilot validates the workspace and management foundation; it does not imply unrestricted autonomous AI execution or general commercial availability.
PROJECT LOCATIONS
Amsterdam.
Düsseldorf.
Two European locations form the geographic scope of the project. Infrastructure development and platform work are brought together within the same personal-assistant initiative.
Amsterdam
The Netherlands location within the project’s infrastructure footprint.
Düsseldorf
The Germany location within the project’s infrastructure footprint.
The location overview describes the project scope. Cross-site failover, service-level commitments and regional capacity will be defined as the platform matures.
ACCESS & CONTROL
Personal access.
Clear boundaries.
A useful assistant should work inside a defined environment. Separation between customers, projects and operators is part of the platform design from the beginning.
Your own workspace.
Tenant-scoped accounts and project permissions separate customer resources. A customer workspace is not an administrative entrance to the underlying infrastructure.
Explicit connections.
Personal integration keys are encrypted. Optional connections are managed separately from the base workspace, with access limited to the intended project and service.
Access has an end.
Provisioning and return are controlled operations. Access revocation and data-preservation checks are part of pilot qualification before an environment is issued again.
DEVELOPMENT STATUS
In progress.
Built in stages.
The project has an implemented platform and a controlled pilot. Work continues on assistant execution, broader operational qualification and the path to a publicly available service.
Implemented & exercised.
- Customer accounts, sessions and tenant-scoped projects.
- Persistent task operations and project activity history.
- Web dashboards and environment observations.
- Encrypted personal integration credentials.
- Controlled Mac provisioning, access, return and reissue on the original pilot machines.
The next delivery stages.
- Provider-backed AI execution and assistant workflows.
- Broader fleet onboarding and operational qualification.
- Further validation of storage, recovery and optional service workflows.
- Mobile delivery beyond the current web experience.
- Commercial terms, billing and public-service readiness.
Overall project status: In progress. Pilot results apply to their tested scope. Availability, pricing and a general launch date have not been announced.
DISCUSS THE PROJECT
A personal assistant.
With a place to work.
Talk to us about dedicated workspaces, project workflows and infrastructure requirements for personal AI assistants.