Home › Platform
The Platform

A Three-Component Platform for Governed Document Generation.

A Word plugin for authoring on existing government forms. A web-based workbench that governs every template through configurable approval workflows. A REST API that accepts JSON and returns governed PDFs. Each component integrates independently with an existing stack and connects tightly enough that approval state, version numbers, and document selection logic flow correctly across all three.

Request a demo See how it connects
Word Plugin
Template authoring
Author
template submission
Approval Workbench
Governance and versioning
Govern
approved version published
REST API
Document generation
Generate
3 Components
5 Feature areas
1 API endpoint
42ms Avg response
Compliance and ops leads
Your approval is the gate. Nothing goes live without your sign-off on record.

Every template version must complete a configurable workflow before it can generate a single document. Sequential, parallel, or conditional routing. Every action timestamped. When a regulator asks which version was live on a specific date, the workbench answers in seconds.

See what this means for compliance teams
Developers and engineers
One endpoint. One payload. Document selection logic out of your codebase for good.

JSON in, governed PDF out. The rules engine handles document selection at generation time no template IDs required in the request. When a regulation changes, compliance updates the workbench. No deployment from you.

See the developer documentation
Platform and ISV builders
One integration. Every client gets their own governed environment from day one.

Full tenant isolation every client's templates, workflows, users, and documents completely separate at the database level. Onboard a new client, they inherit the governed infrastructure. No per-client engineering work.

See the ISV and builder solution
How It All Connects

The Complete Data Flow,
End to End.

Most document automation platforms stop at generation. Templx is designed around the handoffs: between authoring and governance, and between governance and generation. Those handoffs are where compliance risk lives.

Full platform data flow
Word plugin
Workbench
REST API
Word plugin
Template authored
Compliance team maps placeholders onto government form in Word sidebar
Placeholder catalog
Fields pulled from tenant-scoped catalog. Calculated and conditional fields configured.
Submitted for approval
Author submits from plugin. Workbench receives and queues for workflow.
template submission
Approval workbench
Workflow triggered
Configured workflow fires. Stages routed sequentially, in parallel, or conditionally.
Reviewers sign off
Role-based assignment. Escalation on timeout. All actions timestamped to audit trail.
Version published
On full approval, template is versioned and published as active. Previous version archived.
approved version
Rules engine (config)
Conditions defined
Business users configure which templates fire under which conditions: state, type, value, any payload field.
Rule set active
Rules stored in workbench. Evaluated at generation time against incoming JSON payload. No application code required.
rule evaluation
REST API
JSON payload received
Calling application sends payload. Tenant identified. Rules engine evaluates conditions against payload fields.
Template selected
Matching approved template version retrieved. Only approved versions are eligible for generation.
PDF returned
Data merged into template. Governed, correctly formatted PDF returned in response body. Avg 42ms.
Author submits
Triggers workbench workflow. Author cannot publish directly no single person controls both authoring and publishing.
Workflow completes
Template versioned and published as active. The API serves only the current approved version no override exists.
API receives payload
Rules engine evaluates conditions, selects approved template, merges data, returns governed PDF. Avg 42ms.
Built For Multi-Tenant Deployments

One Platform.
Complete Tenant Isolation.

Tenant isolation is an architectural decision in Templx, not a configuration option. Every data-bearing resource (placeholders, templates, workflows, users, documents) is scoped to a tenant at the database level. Nothing crosses tenant boundaries.

Login determines tenant context. When a user authenticates, the platform resolves their tenant and serves only that tenant's resources. The Word plugin, the workbench, and the API all operate within the same isolation boundary.

  • Separate placeholder catalogs, templates, and workflows per tenant
  • Separate user accounts and role assignments per tenant
  • Separate document generation history and audit logs per tenant
  • Shared platform infrastructure, separate everything data-related
  • API requests are tenant-identified. No payload from one tenant can access another
See the ISV solution
Tenant isolation model Shared infra · Isolated data
Shared: Platform infrastructure Word plugin API endpoint
First National Bank
47 templates 3 workflows 12 users 6 placeholders
Applied Insurance
23 templates 2 workflows 8 users 9 placeholders
Your organisation
templates workflows users
No data is shared between tenants. Zero bleed by architecture.
Works With What You Already Have

One Endpoint.
Any Calling Application.

The API is calling-application agnostic by design. Loan origination systems, banking platforms, insurance administration systems, wealth management platforms, and custom internal tools all integrate the same way one endpoint, one payload shape, one PDF response. The diagram shows the range of systems that can connect without any platform-specific configuration.

There is no CRM dependency, no platform migration, and no lock-in. If your application can make an HTTP request, the integration is straightforward. Most engineering teams complete it in an afternoon.

Developer documentation
Calling application types
Loan origination system
Banking platform
Insurance admin system
Wealth management platform
Any HTTP client
JSON payload · POST /api/v1/generate
Templx API
Rules evaluated · Template resolved · PDF generated
Governed PDF · 200 OK · avg 42ms
Calling application receives governed PDF
Platform By The Numbers

Architecture Depth,
Not Just Feature Count.

4
Workflow node types
Sequential, parallel, conditional, and escalation, combinable in a single workflow
5
Placeholder types
Text, calculated, conditional, fragment, and repeating section, all manageable from the Word sidebar
3
Approval routing options
Assign by named user, by role, or by direct email address, per stage, per workflow
42ms
Avg API response time
Governed PDF returned directly in the response body
100%
Audit trail coverage
Every template change, every approval action, every published version, logged with timestamp
Complete
Tenant isolation
No data shared between tenants at any layer: placeholders, templates, workflows, documents, users
1
API endpoint to integrate
One endpoint, one payload shape, one PDF response. The full integration is a single afternoon
0
CRM dependencies
No Salesforce, HubSpot, or proprietary platform required at any layer of the stack
Platform Features

Five Feature Areas.
One Connected Platform.

Each feature area has a dedicated page with full capability detail. Select what matters most to your role.

Template Authoring
Word add-in for mapping data fields onto existing regulatory forms. Non-destructive floating placeholders, no layout changes.
Full feature details
Template Management
Full lifecycle control version history, approval state, usage analytics, and metadata tagging, per tenant.
Full feature details
Document Generation
REST API JSON payload in, governed PDF out. Works with any calling application. No CRM required. Average response under 50ms.
Full feature details
Approval Workflows
Visual workflow designer sequential, parallel, or conditional routing, escalation engine, full audit trail. No template goes live without sign-off.
Full feature details
Rules Engine
Which documents generate under which conditions configured in the workbench by business users, not in your application code.
Full feature details
Get Started

The Platform Your Regulated Workflows Have Been Missing.

Author in Word. Govern with workflows. Generate via API. One platform, connected by design.

Request a demo

Up and running in days, not months.

See it applied to your industry · Developer documentation