Triggers
Start on a schedule, an inbound event, a form submission, or an API call from another system.
e.g. a tasker arrives · a form is filed
Workflow & automation
Build the workflows only your agency runs.
Workflow iQ is Feith's BPM engine for the agency-specific processes the shipped products don't cover: approvals, taskers, routing, reviews. Model them in a visual designer; every step then runs inside your security boundary, enforces identity and clearance, and writes to one audit trail.
The gap A process you run That no product ships.
model
Workflow iQ Model the process Triggers, decisions, approvals, SLAs.
run
Your boundary It runs where you do On-prem to air-gapped IL6.
The custom processes between your systems (approvals, taskers, routing, reviews) modeled once and run inside your own boundary, under your identity and audit controls.
IL6 highest deployedAir-gapped and deployed today
4 ways to run, one definitionOn-prem · agency cloud · FedRAMP · air-gapped
$0 per executionShips with every Feith application license
ABAC enforced per stepIdentity and clearance checked on every action
Per-instance licensing: Workflow iQ ships with every Feith application license. No per-execution charges, no premium-connector surcharges.
Why a purpose-built engine
A BPM engine for sensitive processes.
The processes that carry classification, clearance, and chain-of-custody requirements, and can't run on a shared, internet-facing platform.
Build any process
Model the agency-specific workflows no product ships (triggers, forms, decisions, approvals, SLAs, integrations) in the visual designer.
Learn moreGoverned by the platform
Every step runs in a user identity, enforces ABAC, and writes to a tamper-evident audit log. It reaches the Feith apps, the vault, and external systems through governed APIs.
Learn moreDeployable wherever the work lives
On-prem, agency cloud, FedRAMP, or air-gapped up to IL6: single-tenant in every deployment, one definition everywhere.
Learn moreBuild any process
Model any process. Visually.
Workflow iQ is a visual designer and execution engine for government processes. Drag in triggers, forms, decisions, approvals, and integrations; set the routing and the deadlines; deploy. A leadership data call is the kind of process no product ships out of the box, so an agency models it in Workflow iQ itself.
A leadership data call, end to end
Trigger Data call arrives Leadership issues a tasker with a deadline.
Form step Capture the tasker A custom intake form records the scope, the owner, and the due date.
Decision Which offices own it? The workflow branches to the responsible offices.
Branch: assign by office
AssignPolicy
Assign to the policy office AssignField
Assign to the field office TrackSLA · 10 days
Track responses against the deadline Escalate any office that runs late. Then: close it out
ActionConsolidate the responses
ApprovalRoute for concurrence
ActionNotify offices & archive
The building blocks
Forms & queues
Capture structured input and route work to the right person or office.
e.g. an intake form · an office work queue
Decisions & branching
Route on any data the workflow holds: values, dates, roles, prior steps.
e.g. branch by office, amount, or priority
Approvals & SLAs
Multi-level sign-off, parallel concurrence, escalation, and deadline tracking.
e.g. supervisor → budget → final approval
Integrations
Read and write external agency systems and the Feith applications through governed APIs.
e.g. look up a record · open a case
AI steps (optional)
When a step needs to read, classify, or summarize content, it can call Prompt Runner: bring-your-own-model, inside your boundary.
e.g. summarize an inbound response
Example processes
Leadership data call Correspondence & taskers
1 When A data call arrives from leadership.
2 Do this Assign tasks to the responsible offices with due dates.
3 Then Consolidate the responses and route them for concurrence.
System access request Access & identity
1 When A staff member requests access to a system.
2 Do this Route to the manager, then security, for approval.
3 Then Trigger provisioning and notify the requester.
Travel & purchase approvals Internal approvals
1 When An employee submits a travel or purchase request.
2 Do this Route to the supervisor, then to budget.
3 Then Record the decision and notify everyone involved.
Governed execution
Every step, governed.
A workflow runs as part of the platform itself. Every step executes in a user's identity, under ABAC, recorded to the audit log, and reaches other systems through governed APIs.
Runs as a user
Every step executes in the identity that started it, with no shared service account quietly widening access.
ABAC on every step
A step can't read, route, or write a record the user's attributes don't allow. Classified material can't surface in an unclassified output.
One audit trail
Every step, decision, approval, and AI call writes to a tamper-evident log, with the attributes in effect at each step.
Governed integration
Reaches the Feith apps, the records vault, and external systems through governed APIs: federated identity, in-boundary, nothing crossing the perimeter.
In the designer
Visual canvas for the whole workflow
Drag-and-drop steps, decisions, approvals, and forms
Live preview as you model the flow
Version control and rollback
Test mode runs against real data
Deploy without recompiling or redeploying code
Runs where the work lives
The engine runs where you do.
Workflow iQ deploys wherever your work already lives (on-premises, agency cloud, Feith's FedRAMP Moderate cloud, or air-gapped up to IL6), single-tenant in every case, and the same definition runs everywhere.
Deployment matrix
| Environment | Where it runs | AI models (optional) | Footprint |
|---|---|---|---|
| On-premises | Your datacenter, your hardware | Local or air-gapped models | 30+ agencies |
| Agency cloud | Your cloud subscription | Cloud models in the same boundary | 15+ agencies |
| Feith FedRAMP cloud | Feith's FedRAMP Moderate cloud | Models inside the FedRAMP boundary | Authorized environment |
| Air-gapped / IL6 | Inside the enclave | Models inside the enclave | Classified deployments |
Where horizontal BPM falls short in federal environments
| Capability | Horizontal BPM platformsMulti-tenant SaaS · commercial cloud · execution-priced | Workflow iQ |
|---|---|---|
| Single-tenant deployment | Multi-tenant SaaS by default; single-tenant needs an enterprise tier and isn't available everywhere | Single-tenant in every deployment, no exceptions |
| Air-gapped deployment | Limited or not available | Native: the engine runs fully inside the enclave |
| IL6 ATO | Vendor roadmap or partner-dependent | Deployed at IL6 today |
| AI model isolation | LLM calls leave the platform boundary to a vendor-hosted model | If a step uses AI, the call stays inside your security boundary |
| Runs with your records platform | Generic content store; reaches records systems only through external connectors that cross the boundary | Runs inside the Feith platform: workflows reach the Feith apps and records vault through governed APIs, in the same boundary |
These are the conditions horizontal platforms can't serve cleanly: classified networks, CUI, IL6, single-tenant isolation. The engine was built for them.
Across your platform
One custom workflow. Across your platform.
A custom workflow reaches the Feith applications, the records vault, and your agency's own systems through governed APIs, in one execution, one audit trail, inside one boundary. The applications stay productized; the workflow is your glue.
One workflow, integrating across the platform
1Custom trigger
An agency intake form is submitted Trigger 2RMA iQ
Read the related record through the API Integration · read 3Case Manager
Open a review case through the API Integration · write 4Notify & log
Email the offices, write one audit entry Action Audit log
Horizontal platforms can't do this in a federal environment. Power Automate orchestrates Microsoft 365; Appian and ServiceNow build on their own stacks. None sit inside the same accredited boundary as NARA-certified records, FOIA, and declassification applications. Workflow iQ does, because Feith does.
The Feith applications it integrates with
Common questions
What buyers actually ask.
BoundaryDoes Workflow iQ count toward our FedRAMP boundary?
Yes, when the agency runs Feith in the FedRAMP cloud, the engine is part of the FedRAMP-authorized environment. On-premises or in an agency cloud, the boundary is whatever the agency defines. The engine inherits the boundary of the deployment, not the other way around.
LicensingWhat is the licensing model?
Per-instance. Workflow iQ ships as part of every Feith application license, so there's no separate workflow-engine license to buy, and no per-workflow or per-execution charge. Agencies running multiple Feith applications get one engine across all of them at no additional license cost.
ExecutionHow long to stand up a new workflow?
A standard workflow can be modeled and tested in days; advanced multi-step integrations or custom AI steps take longer. Training runs about a week for designers and two for advanced builders, and Feith engineering stays available for complex architecture.
SecurityHow does ABAC work inside a workflow?
Every workflow step runs in the context of a user identity and inherits that user's ABAC attributes. A step can't read, route, or write a record the user lacks clearance for, so classified material can't leak into an unclassified workflow output. The audit log captures the attributes in effect at every step.
AI modelsWhen a workflow uses AI, whose models run it?
Your choice. The optional AI step calls Prompt Runner, which is bring-your-own-LLM: cloud-hosted models (Anthropic, OpenAI, Google), customer-hosted models in agency cloud, on-premises models, and air-gapped models inside classified enclaves all work. The platform requires no specific model and doesn't charge for the model layer.
Next steps
Show us your process. We'll sketch the workflow live.
A working session is the fastest way to see how a Feith workflow fits a process your team runs. Bring an example process. We'll have it on the designer canvas before the meeting ends.
Contract vehicles
GSA Schedule 36 SEWP IWRP DOC CATTS FedRAMP Marketplace
Request received.
A Feith engineer will reach out within one business day to schedule the working session. Bring the example process you would like sketched live in the designer.