Spark ERP

AI · Prompts

Change the wording. Not the code.

Prompts live outside your code as versions. A label such as prod decides which version callers get, so releasing and rolling back is moving a label. A playground runs the prompt on your real models before you release.

Book a demoAI Studio
Prompts in Spark ERP Your ERP dataModel providerPermissions Your ERP dataModel providerPermissions Audit trailAsk or trigger Human approvalProposes
Prompts and its guardrails
Your ERP dataModel providerPermissionsAudit trailHuman approvalPrompts
How Prompts works with you
Ask or trigger

A user request or event

1Grounded

Uses your own records

2Proposes

A draft, not a silent change

3You approve

Within your permissions

4Logged

Recorded for audit

5

What you can do

Variables

Write prompts with values that change per call.

Versions

Every save is a new immutable version; nothing is overwritten.

Labels

Callers ask for prod. Moving the label is the release and the rollback.

Playground

Run on your real model profiles, with time and token counts.

Compare

Run on more than one model and see the answers side by side.

See what changed

A diff shows exactly what differs from the version before.

The real screens

The prompt editor with a system message, a user message with variables and a playground showing a real answer.
Edit and try: the playground runs on a real model.
The versions of a prompt with their labels.
Versions and labels.

Release wording like you release software.

Versions, labels and tests, without a deployment.

Book a demoRAG pipelines