The same project board
Projects, tasks, timesheets and plans work exactly as in the cloud. People on an installation do not get a cut-down version.
- Boards, timelines and lists
- Time tracking and approvals
- English, Turkish and German
Plan and deliver
Measure and automate
By team
By need
Project management tools
Time tracking tools
On-premise & data control
Akollo runs in our cloud, in your own cloud account or in your own data centre. It is the same product in all three. You decide where the data lives, what may leave the network and where the AI runs.
Same product as the cloud · nothing leaves without a rule
The installation is the same product as the cloud. These are the decisions your infrastructure and security teams make on the way.
Our cloud, a dedicated environment in your own cloud account, or servers in your data centre. Your teams plan and track work the same way in all three.
The guide sizes the web application, background jobs, database, backups and monitoring for a pilot, 1,000 or 5,000 people. Without an AI model, no graphics card is needed.
Connectors such as directory sync reach only the hosts your administrators allow. With no allowed list, they reach nothing at all.
Connect your own model server or provider key, use Akollo's models, or switch AI off. Data classified as restricted never goes to an outside model.
One retention rule per kind of data, and an audit log of every privilege and configuration change for your security team.
Regulated industries
Some teams cannot put project, time and people records in a shared cloud, however good the product. Akollo installs where their rules say it must, and keeps the evidence their auditors ask for.
Change, IT and regulatory projects on your own servers, with an audit trail for internal audit and the regulator.
Projects and working time without an outside cloud, with retention that follows your records policy.
Staff and project data inside your own network, with sensitive fields hidden or masked by role.
Project teams get the full product. Administrators get the screens that keep the installation inside your rules.
Projects, tasks, timesheets and plans work exactly as in the cloud. People on an installation do not get a cut-down version.
Changes to privileges and configuration, with who made them and when, for administrators and your security team.
Add your own provider key or model server, choose which level of data may go through it, then test it before it goes live.
One rule per kind of data, from screenshots to exports, checked against the notice your employees acknowledged.
Akollo AI can run on a model server you control, on your own provider key or on Akollo's models. It reads only what the person asking may see, and asks before it changes anything.
Summarise this week's status of the core systems programme.
Five of seven projects are on track. The data migration has slipped a week and the network upgrade waits for a supplier. Shall I draft the steering note?
Ask Akollo AI
Try asking
Data classified as restricted is answered only by a model inside your installation; if there is none, the request is refused. You can also switch the assistant off completely.
See what the assistant can doNo promises to take on trust. These come from the installation and the settings your administrators control.
Which external hosts connectors may reach, set once for the installation and narrowed again in each connector's own settings.
Where you see itSecurity settings
Every AI request is recorded with the model it used and how much it used, never with the question or the answer.
Where you see itAdmin → Usage
Who changed which role, permission or setting, and when, so a review starts from the record instead of from memory.
Where you see itAdmin → Audit records
The retention rule for each kind of data, and how it compares with the notice your employees read and acknowledged.
Where you see itRetention and deletion
No. An installation in your data centre or your cloud account is the same product as our cloud, with the same modules and the same three languages. The difference is who runs the machines and who sets the network rules.
No. An on-premise installation runs inside your network. Connectors cannot reach any external host until your administrators allow it, and the assistant can be limited to models inside the installation or switched off.
Not for Akollo itself. The application, background jobs and database run on ordinary machines. A graphics card only matters if you run the larger AI models on your own hardware, and the installation guide sizes that for you.
Yes. Connect your own model server, directly or through the AI Connector, which connects out from your network so no inbound port is needed. Running every model, including the large ones, inside the installation is planned and already documented with hardware profiles.
How the assistant handles your dataOnly in a support session, which your organisation sees as a banner. A support session can read the pages it is allowed to, but cannot create, change, approve or delete anything, and sensitive fields stay hidden.
Security & trustWe will go through hosting options, sizing and network rules with your IT and security teams, and agree a first team to start with.