Oria is the interface
Your team asks for the application, builds it in a session and uses it. One place for the request, the build and the daily work.
Oria keeps the tenders that fit what your company sells, extracts the entity, scope, amount and closing date, and turns the requirements into a checklist your team works through together.
Portals, categories, what you sell, who prepares the bids. A specialist answers.


Every screen on this page is an application built with Oria and running on a company's data. Figures are the ones of that company or of a demo; none of them is a promise about yours.
The tenders are public. The problem is the volume, the number of portals and the length of each document.
The team decides what to bid on. The application reads, extracts, scores and keeps the dates, so the decision is made with the facts in front of it.
The portals you follow, the tender documents, and your company profile: what you sell, your capacity, your certifications.
What a fit is for you, who evaluates, who decides on a bid, what the checklist must cover and who sees which tenders.
The tender radar opens in your governed workarea. Sales and bids work from it; your CRM stays as it is.
The application complements the systems you already run. It does not ask you to replace the ERP or the CRM: they stay the source of record, and Oria writes back to them only through the governed actions you define.
Oria is the interface for asking, building and using business applications. ARPIA is the operating system underneath: the data, the models, the permissions, the rules, the audit trail and the infrastructure that make the application safe to run.
Your team asks for the application, builds it in a session and uses it. One place for the request, the build and the daily work.
It connects your data and systems, the models, permissions, rules, audit and infrastructure. The application runs on it; your systems stay the source.
Anthropic, OpenAI, Gemini, open models or your own: assigned by configuration. Change the model and the application keeps working; nothing is rebuilt.
Data, business logic, applications and the record of every action remain under your company's control, in your workarea or your datacenter.
Oria is the application layer of the ARPIA Enterprise AI Operating System. How the operating system works, on arpia.ai →
ARPIA holds SOC 2 Type II and ISO 42001, both audited by A-LIGN across the platform Oria runs on. The reports are available on request.
In your workarea, on infrastructure ARPIA runs in the region you choose at signup: LATAM, the United States or the United Kingdom. For a higher bar, the platform deploys inside your datacenter. Your systems stay the source; Oria works on a governed reflection of them.
No. ARPIA runs isolated from the model providers under zero data retention contracts, and each workarea is its own tenant.
What you define. Every person opens the application with their own permissions inside the workarea: the Pro seat that built it shares it, and each seat sees the data its role allows.
Oria builds on the systems you already run and the files you provide: databases, exports, documents, APIs. The application reads live data from them and writes back only through governed actions, with approval where you want it.
Every action, with who ran it, on what data, with which model and at what cost. Oria never writes to your live systems on its own.
Yes, by configuration. The application is built on your data and rules, not on a model, so a new model does not mean a new application.
The ones you follow: you name them in the session and provide the documents, and the application is built around them. The screens on this page come from a demo built on generated data in the formats of PanamaCompra, SECOP II and SICOP.
It prepares the material: the requirements as a checklist, the dates, the amounts and the comparison between tenders. Your team writes the bid with that in front of it, and a person decides what is submitted.
Against your company profile: what you sell, the amounts you can take on, the certifications you hold. You see the score and the reasons behind it, and you can change the profile at any time.
Yes. Each tender has a status, and the pipeline is shared inside the workarea, with each person's permissions.
No. It complements it. If you want the bids you win to land in the CRM, that is a governed action you define, with approval where you want it.
It is built in a session with Oria. How long that takes depends on your data, your rules and how many systems are involved, so we would rather see your process first than promise a number.
A Pro seat at $50 per user per month to build and share, Basic seats at $15 per user per month to use the application, and a prepaid wallet for the AI that you size and cap. Every new workarea starts with $100 of credit, and nothing is charged until you add billing details. Prices on the home page.
Create a workarea and build it yourself with $100 of credit, or send the form and review the case with the team first.
Pricing: a Pro seat at $50 per user per month, Basic seats at $15, and a prepaid wallet for the AI. Nothing is charged until you add billing details.