IN DEVELOPMENT · AI-IDEENSCHMIEDE

AI acts.
You decide.

AI protection against AI attacks

We are developing AI-Certain as an independent control layer between AI assistants and the data, applications and APIs they want to access.

This interface is a demo. Technical protection will depend on the security core and verified integrations.

ACTION CHECKConcept example
An assistant requests an actionReview tomorrow’s reservations
AI-CERTAIN

Check first.
Then execute.

TaskPermissionsData & destination
AllowWithin scope
HoldApproval needed
BlockBoundary breached
Enforced boundaries outside the AI model.
01 / OUR APPROACH

Responsibility
stays with people.

An AI assistant can analyse information and propose actions. AI-Certain is designed to check whether a requested action fits the task, which permissions apply and what data would leave the system.

Our security approach combines technical boundaries with decisions you can understand. Critical actions are held or blocked. Approval stays with the user wherever their rules require it.

Our principleAn AI must not expand its own permissions or disable its own safeguards.
02 / PLANNED FEATURES

A framework for
your AI assistants.

These building blocks guide our development.

01

Your rules

Define which data may be used, which destinations are permitted and which actions must remain blocked.

02

Tasks & permissions

Give each assistant a specific task with appropriate permissions, a time limit and a cost limit.

03

Multiple AI models

Choose models through supported integrations and divide tasks between assistants with separate roles.

04

Specific approvals

Review the exact action and its effects. Each approval is intended to apply once to that specific action.

05

Emergency stop

Stop one or all assistants using a visible button or your personal stop phrase through your authenticated control channel.

06

A clear activity log

Track what was requested, allowed, held or blocked, with clear reasons.

03 / HOW IT IS DESIGNED TO WORK

One task.
Three clear boundaries.

Example task: “Review tomorrow’s reservations.”

Choose an action to see the intended decision.

ALLOWED

Reading is part of the task.

The assistant may read the required reservations. Access remains limited to the defined scope.

Rule: reading the required data is allowed
CONCEPT EXAMPLE · NO REAL SYSTEM ACTION
04 / OUR WORK

Building control
step by step.

AI-Certain is being developed at AI-Ideenschmiede. We combine human experience with AI as a tool and review the results of our work.

Our goal is an understandable security solution with technically enforced rules. A second AI can provide additional insights. Binding access limits are intended to be enforced by the independent security core.

More about AI-Ideenschmiede
  1. DEVELOPED

    Concept & interface

    Rules, permissions, models, approvals and emergency stop controls have been developed as a concept and interactive demo.

  2. NEXT STEP

    Security core & first integration

    Check actions on the server and execute them under control. Permissions and stop controls must be enforced independently of the assistant.

  3. PLANNED

    Test, measure, improve

    Test permitted and prohibited actions, manipulation attempts and failures. Use those results to build further integrations.

05 / ONE CORE, SUITABLE INTEGRATIONS

AI-Certain and AILENDO Guard.

STANDALONE SOLUTION · PLANNED

AI-Certain

The shared security core and management interface for connected AI assistants and systems.

INTEGRATION · PLANNED

AILENDO Guard

The same approach, with rules and interfaces for AI features within AILENDO. The user stays in control.

06 / FREQUENTLY ASKED QUESTIONS

What you should know today.

Is AI-Certain already a finished security product?

We are still in development. The integrated interface demonstrates the controls using sample data. It is not connected to an AI model or production system and does not block real attacks.

What does “AI protection against AI attacks” mean?

We focus on controlled AI actions: manipulated content must not give an assistant extra permissions. AI-Certain is designed to enforce the user’s boundaries independently of the model. This does not require identifying an attack as “AI-generated”.

Can I use several AI models at the same time?

That is planned. Assistants can be assigned different models and roles. Communication between them is intended to follow the same data and permission rules. Supported models will be determined through verified integrations.

Can the emergency stop undo everything?

The planned stop blocks new actions. Cancelling an action already in progress depends on the relevant interface. Data already sent and actions already completed cannot be reversed by the stop.

Which systems will AI-Certain protect?

Protection is planned for actions routed through controlled integrations. Each integration requires its own technical verification. Websites, servers and user accounts also require standard security measures against general attacks.

When can I buy AI-Certain?

A release date and price have not yet been set. Distribution is planned through Ailorium. The demo is free to explore.

07 / INTERACTIVE DEMO

Try the controls.

Choose models, draft rules and tasks, review an approval and test the emergency stop. Everything runs locally with sample data. Settings are temporary and do not enforce real security rules.

Open demo in its own view
Control for your AI assistants
Demo: monitoring active
Workspace · AI-Ideenschmiede

Security overview

Interactive concept · Sample data · No connected systems
CONTROLLED ACCESS · DEMO

One action needs your decision.

Your boundaries are defined. One reservation change is on hold; an external data export is blocked. All values below are simulated sample states.

ACTIVE ASSISTANTS
2
Separate roles and permissions
PENDING APPROVALS
1
Waiting for your decision
BLOCKED ACTIONS
1
No data transferred
ACTIVE RULES
3
No expansion by assistants

Assistants & tasks

AAILENDO assistantActive
Model A · Cloud · Sample assignment
Task: review reservations
READ + REQUEST CHANGES
RReview assistantActive
Model B · Cloud · Sample assignment
Task: review change drafts
READ ONLY

Recent security events

Blocked
Customer data export blocked

Destination not permitted · Outside task scope

On hold
Pickup time change on hold

Waiting for one-time user approval

Allowed
Reservations read

Within task scope · Read permissions checked

DECISION REQUIRED
Approval required

Change pickup time

Reservation R-1042 · 5 October 2026

10:00 → 11:00
Data
Pickup time only
Recipient
No external recipient
Approval
Once, for this change

Enforced boundaries

01
Customer data stays in the system

External recipients are not permitted.

02
Permission changes are blocked

Assistants cannot expand their own access.

03
Changes require user approval

A specific action, checked before execution.

Sample state · No AI models or systems connected
Developer: AI-Ideenschmiede · Distribution: AiloriumAI-Certain · Demo 0.7.0
PEOPLE + AI + CLEAR BOUNDARIES

Take a closer look
at our work.

Explore the interface and see how rules, approvals and stop controls are designed to work together.