Questions buyers ask
About setup, the AI, approvals, security, Arabic and pricing. Anything else, write to info@portusai.co.
Getting started
No. You describe a workflow in a sentence, the way you’d brief a new hire, and the builder drafts it as a map of steps and practises it on sample data.
You change it by asking the co-pilot or by editing the map. Nothing goes live until someone with the permission to do so makes it live.
How the builder works15 in all: screening CVs and inviting candidates to interview, recording a hire, the offer letter, onboarding, setting up a new payee, leave requests, expense claims and their export for payment, invoice checks, and an employee’s leaving settlement and clearance.
Recording a hire starts the offer letter, which starts onboarding, which starts setting up the payee, each after its own approval.
See every workflowWe set Portus up with you, one workflow first: usually the one your team runs most often. Once it runs on your real requests, we add the next.
How long that takes depends on your policies and approvers, so we agree it with you on the demo rather than promise a number here.
Yes. Leave starts from Saudi Labour Law and expenses from a starter policy. Under Settings, Policies you change the leave types, their days and who approves them, and the expense categories, their limits and the amount above which finance approves too.
Your weekend and this year’s public holidays go there as well, and every change is kept in the history.
Portus sends email with calendar invites, messages through Slack, Microsoft Teams and WhatsApp Business, and documents for signature through DocuSign.
It can read from and write to any other system with a web API, using a key you save once. Portus keeps the key encrypted and the workflow never sees it. Another system can also start a workflow by sending it data.
The AI
Anthropic’s Claude models. Every run shows what its AI cost, and Analytics adds it up by workflow.
No. An email, a calendar invite, an export or a message to someone outside waits for a person to approve it first.
The approval card names what goes out and to whom, and its button says the action, such as “Approve leave and email Sara”.
It can, so Portus is built for a person to check. Each step’s result is on the run page, a new workflow is practised on sample data before it goes live, and nothing leaves until the person who owns the decision approves it.
The card is built from the exact call that will run, not summarised by the AI, so what the approver reads is what goes out. If the draft is wrong, they ask for changes in their own words and see the new draft before anything is sent.
In a workflow, only what a step sends it: the CV it is scoring, the receipt it is reading, the request it is checking.
In Ask Portus, it works as the person asking, within their organisation and role, so it sees only the runs and workflows they can already see.
No. Under Anthropic’s commercial terms, data sent to its models through its API is not used to train them.
Approvals and control
Each approval step names a role: the hiring manager for interview invitations, the HR manager for leave, the line manager for an expense claim and finance as well above the policy’s threshold.
Only people holding that role can decide it. Portus emails them when something waits, and reminds them if it keeps waiting.
Your decision is bound to the exact content you saw: the recipients, the message and the attachments. If any of it changes before you decide, the card says so and marks what changed.
No. Every send is written to a ledger. If a step runs again after a failure or a restart, Portus sees what already went out and does not send it a second time.
Yes, in your phone’s browser; there is no app to install. The email telling you something waits carries no details, only a link: you sign in and decide on the card itself.
With a passkey, signing in and approving take Face ID, your fingerprint or the phone’s PIN.
Portus retries on its own first. If it still fails, the run page says in plain words what happened and what did not, and someone can try again from that step without starting the run over.
Security and data
On Amazon Web Services, in data centres certified to ISO 27001 and SOC 1, 2 and 3, on encrypted disks. The database and the file store cannot be reached from the internet, and the server has no SSH: it is administered through AWS Systems Manager, with every command logged.
How Portus is securedIt is health checked every 30 seconds from several locations around the world, and an alarm reaches us the moment a check fails. Every service restarts itself if it stops, and a new release that fails its checks is taken out and the one before it put back on its own.
The status page shows the uptime we measure, day by day for the last 90 days.
How Portus is built to stay upPeople in your organisation, by the roles you give them. Each organisation’s data is kept apart in every table, so no row can point to another organisation’s.
The AI sees only what a step sends it. Every change to workflows, roles and policies is kept in the audit history.
A full backup of the database and every file every six hours, encrypted and kept 14 days in Amazon S3, which stores each copy across several data centres. The server can add backups but can neither read nor delete them. A snapshot of the whole disk is taken daily as well, and the last seven are kept.
Portus itself is not certified today. It runs in AWS data centres that are certified to ISO 27001 and SOC 1, 2 and 3, and the trust pages say exactly what Portus adds on top: encryption, backups, monitoring and who can reach what.
Read the trust pagesYes. On request we delete your organisation’s data, and it is gone from backups within 14 days. You can also choose how long run details are kept.
What Portus keeps, and for how longArabic and the Gulf
Yes. Every screen and email is written in Arabic for Arabic readers and laid out right to left, and each person chooses their language.
When a message is written in one language and the approver reads the other, the card can translate it for them to read. What is approved and sent stays the message as written.
Yes, to start with: annual, sick, marriage, bereavement and the other leave types, with the days and pay the law sets. The leaving settlement works out the end-of-service award by the same law.
You change the policy where yours gives more.
Amounts show in riyals with the riyal sign, and numbers and dates in the reader’s own digits. Each organisation sets its time zone, its weekend and its public holidays, and leave is counted by them.
Pricing and buying
We quote after a demo, based on the people using Portus and the workflows you run. The plans are Team, Company and Group.
See the plansThe demo is where you try it, on your own workflow. Bring one your team runs every week; on the call we build it in Portus with you and practise it on sample requests.
Yes. The Team plan covers one business area, HR or finance, and you add the others when the first one runs well.
It depends on the workflow and the documents it reads. Every run shows its AI cost, and Analytics totals it by workflow and by business area.
Bring one workflow your team runs every week
On the call we build it in Portus with you, in Arabic or English.
Or write toinfo@portusai.co