Welcome to the AI Portal
One governed entrance to AI for your whole organisation — chat with agents that search your documents, call approved tools and write things you keep.
The ECV AI Portal is an enterprise AI portal for organisations that run on AWS. You chat with agentsAgentAgentAn assistant with its own instructions, knowledge, tools and default model. Every chat runs through one — plain chat is an agent that used no tools.Open in glossary that search your documents, call approved tools and write things you keep. Your organisation decides who reaches what, which models are available and what each department may spend.
eCloudvalley builds the portal as a product. Each organisation gets its own copy, deployed inside its own AWS account, with models served by Amazon Bedrock. Single sign-on, department budgets, model governance, audit and per-resource visibility are built in. Nothing in these pages needs an AWS, Keycloak or gateway console.
Where do you want to start?
Your first answer in five minutes.
I use the portal Chat, agents, knowledge, artifacts and what you spend.
I administer it People, departments, models, budgets, tools, applications and the audit log.
What each role sees
The rail on the left shows what your role’s capabilitiesCapabilityQuyền hạnPermission to do one kind of thing, such as setting budgets or reading the audit log. Roles are the only way to get one.Open in glossary allow.
| You are | You see |
|---|---|
| A member | Chat, agents, skills and prompts, knowledge, artifacts, and your own Settings (usage, memory, connected apps, model keys) |
| A department lead | The same, plus the few admin screens their role opens (for example Provider keys) |
| An organisation admin | The same, plus the Admin console |
| The organisation owner | Everything an admin sees |
An administrator’s rail adds Admin console at its foot, with a chip such as 3 to review when something waits for them. Department budgets and spend live in that console. Your own Usage & budget, Memory, Connected apps and Model keys live in Settings, opened from your name at the foot of the rail — see What’s where.
There is exactly one organisation per deployment, so there is no organisation switcher and no billing, plan or seat screen.
Three ideas behind the product
Key rules
- An agent is a bundle. An instruction, a model, the tools it may call and the knowledge it may read. Plain model chat is just an agent that called no tools.
- A department is a budget. Everybody belongs to exactly one departmentDepartmentPhòng banThe bucket that pays: it owns a budget, limits and which models its people may use. Everyone belongs to exactly one.Open in glossary, and every request is costed there. Permission comes from your built-in role plus custom roles held directly or through groupsGroupNhómA set of people used to give roles and to name in sharing rules. A person can be in many groups; a group never holds money.Open in glossary.
- Deny always wins. Agents, skills, prompts, applications, artifacts and knowledge bases each carry visibility rulesVisibilityQuyền xemA resource's own sharing rules: who can find and use it, by department, group or person. Seeing a resource never grants extra permissions.Open in glossary, and a deny beats any allow.
Next
Start with the Quick start, or read Sign in. If your organisation’s portal has just been deployed, an administrator starts at the first-run wizard.