Developers frequently rely on multiple GenAI-powered applications to handle various use cases, with each application comprising several components that utilize LLMs for different tasks. Gegentica is built to seamlessly protect and operate across every part of your application that leverages GenAI for your agentic systems.
Gegentica organizes governance around a simple hierarchy: Organization → Project → governance resources.An organization is your company or team. Within it, a project scopes everything to a specific application, environment, or business unit. Each project contains:
AI Use Cases — the providers and models a project is approved to use, with a risk rating.
AI Agents — running instances of those use cases, each inheriting its provider, models, and prompt from an approved use case.
Policy Sets — collections of rules that govern what an agent is allowed to send or receive, with a Draft → Pending Review → Active lifecycle.
Access Keys — credentials issued to client applications, scoped to specific agents and prompts.
Org-level Controls and Criteria (compliance framework mappings) and the Audit Log sit above the project level and apply across all projects in the organization.Projects enable you to:
Scope use cases, agents, and policy sets independently per application or environment
Monitor external, customer-facing GenAI applications separately from internal GenAI tools
Compare performance and policy effectiveness across development and production environments
Pinpoint exactly which agent or use case is being targeted or exploited
For instance, you could create a project for your production customer support chatbot and another for your internal employee knowledge base Q&A tool. Alternatively, you might set up separate projects for the test and production environments of each application to monitor and compare them independently.
Customers can manage their projects within the Gegentica app platform user interface. The Projects page allows you to
create new projects and lists each of your existing projects along with its details.Each project is given a unique ID and contains its own AI Use Cases, AI Agents, Policy Sets, and Access Keys.If your application needs different agents to follow different rules, create multiple Policy Sets within the project and apply each to the relevant agents — you don’t need a separate project for that. Reach for a new project when you need to isolate environments, applications, or business units entirely.
When you first sign up for Gegentica, you will be prompted to create an organization and a project. This is a one-time setup process that allows you to start using Gegentica immediately.You can create additional projects at any time through the Projects page in the Gegentica app platform user interface.You can create additional organizations, and during this time you will be prompted to create a project for that organization as well.
The org-level Projects page
The only required field is the project name. The project name must be unique within your organization.You can optionally add a project description to the project, which can be helpful for other users to understand the
purpose of the project.Next, define an AI Use Case for the project, then create a Policy Set from the sidebar. A Policy Set defines the rules and
configurations that Gegentica will use to protect your application.
Click on the three dots next to the project’s name to access options for viewing details, editing, or deleting it.
When you select Edit, a popup will appear where you can modify the project’s name and description, then save your changes.
Admins can delete a project by clicking on the three dots next to the project’s name and selecting the delete option.
Confirm the deletion in the popup that appears.Deleting projects is permanent and cannot be undone. Once a project is deleted, its historic requests will no longer
be linked to any project, meaning they will lose access to the deleted project’s logs and Policy Sets.
Additionally, all Policy Sets, AI Agents, and Access Keys associated with the project will be removed.
Requests using these Access Keys will no longer be protected by the project’s Policy Sets, and will experience errors.
