Everything TechAppForce does, on one map

Define business records and their fields as configuration, with no back-end code.

Link records to each other and save a parent with its children in one step.

Customers add their own fields to a live app with no database change.

Preview the exact database change first; nothing is ever dropped.

Point an app at an existing database and turn its tables and views into managed records.

Every new entity gets ready-made list and detail data sources.

Human-readable numbers such as INV-2609-00001.

Managed lists of values for dropdowns.

Use a database view like a table; saves go to the base table.

Deleted records can be recovered; each relationship decides whether to cascade or block.

Filters with 22 operators, grouped AND/OR logic, "current user" and date variables, totals and grouping.

Reusable data sources for screens, reports, notifications and workflows.

Call existing database logic by name.

Both databases are supported end to end.

New list, detail, filter and layout screens go live with no front-end release.

Build screens visually, bound to a data source, with preview.

Grid, kanban, Gantt, scheduler, pivot, charts, spreadsheet, document editor, file manager, tree, history, comments and more.

Edit in the list and export to CSV, PDF or Excel.

Lists update when data changes.

One screen serves many roles; hidden parts never reach the browser.

Show, hide or require fields based on the record's data.

Add your own UI components with no platform release.

Adjust styling per app, tenant or screen.

Put charts, pivots and totals on any screen.

Built-in console, database viewer and timeline for builders.

Discuss a record and notify colleagues.

Statuses, allowed transitions, rules before a move, history, and automation after it.

Move many records at once.

Track time in status and targets.

Approvers picked by user, role, team, manager, record field, related record, owner or saved query. Sequential or parallel.

Any, all, N of M or percentage, plus matrix and amount-band routing.

Delegate approvals; records lock while pending and re-approve after changes.

A scheduled sweep sends reminders and escalates overdue steps.

Each decision snapshot is hash-chained.

"My pending approvals" for each user.

Act when records are created, edited or deleted, including on specific field changes.

Automate follow-ups: create records, call APIs, send notifications, change status.

Run automation on a cron or one-time schedule.

Run a workflow on demand, optionally returning a file.

Design action chains visually in Studio.

Templated emails from any event.

Text-message alerts.

Real-time alerts inside the app.

Call another system on an event, with retries.

Personalised messages built from record and query data.

Send to the right people; users can opt out of a channel.

See what was sent and to whom.

Attach documents to any record.

Browse, rename, move and search files.

Share a file outside the app with an expiry, a click limit and a revoke option.

Thumbnail previews; edit documents in the app.

PDF, Excel, Word, CSV and HTML from saved queries and templates.

Design and preview reports.

Email reports on a schedule, with a timezone, run history and run-now.

Validate first, then load data, including lookups and child rows, with row-level errors.

Change many records at once.

Find records across the app.

See who changed what and when, including child records.

A history of every status move and trigger run.

Standard sign-in with rotating refresh tokens.

Standard tokens for integrations (client credentials, authorization code).

A second sign-in step.

The tenant admin connects their Microsoft organisation, and staff sign in with work accounts.

Each customer sets MFA, lockout, password expiry and session lifetimes.

Self-service reset with a code; admins can reset passwords.

Each role gets its own read, create, update and delete scope per record type.

Managers see their team's records.

Membership-based access that flows to related records.

Share one record with a user, team or role.

Stored filters per role.

Gate screens and buttons by permission.

Copy a role with its permissions.

Each customer is a tenant that owns or subscribes to apps. Each app has Development, QA and Production environments, and each environment can have its own database.

A new customer signs up, and gets an admin account and a default subscription.

Each tenant gets its own address (for example acme.<product domain>), checked for availability at sign-up. Signing in on it opens that tenant.

People who belong to several customers switch between them.

Plans with price, currency, billing period, trial days and included seats. Draft, publish and archive. Editing a live plan creates a new draft.

Trials of a set length (default 14 days) that end in read-only mode unless the customer pays. The remaining days are kept if they convert early.

Trialing → Active → Past due → Grace → Read-only → Cancelled or Expired. Each state controls sign-in, reading and writing.

Each plan includes a number of seats; adding users beyond the cap is refused.

Customers pay by card or UPI through Razorpay, one-off or auto-renewing.

Customers stop renewal and can change their mind before the period ends.

An invoice for each payment, numbered in sequence per financial year.

Every payment is recorded once and can never be edited or deleted.

Payment events are verified by signature, and a 15-minute reconcile catches anything missed.

Failed payments move the subscription through past-due and grace to read-only.

Plans switch features and modules on or off; the platform refuses what the plan does not include.

Counts usage (records today) for plan limits and billing.

Tenants browse published apps and plans and subscribe. The app is provisioned for them, with an "app ready" message.

A subscriber automatically inherits the app's configuration, and gets their own copy of access rules and template data.

Users see when a trial is ending or a payment is due.

Separate stages, each with its own database connection and pinned version.

See every configuration and reference-data difference between two environments.

Pick changes and promote them, with reference data applied in dependency order and migration scripts carried along.

Build and deploy a release from Studio.

Move a release on to Production.

A documented API for every service.

One API for every entity: records, queries, status, stored procedures.

Publish clean API endpoints for partners or portals, with no code and a generated contract.

Call external systems from workflows and events.

Receives signed payment events.

Write real C# rules that run on every data operation.

Add your own automation steps.

Add UI logic to any screen.

Build a fully branded front end on the TAF back end.

Grid, form, list, inbox, card, metric and more, styled by your brand.

Generate typed clients for your entities and endpoints.

Build extra services on the same foundation.

A standard template for new services.

Platform events flow to automation, audit and search.

A professional development studio for TAF apps.

Sign in once and pick an app.

Open a whole app, see what changed, and choose what to keep.

Visual designers that run the platform's real engines.

More designers with publishing.

Administer the app from Studio.

Check scripts with the platform's compiler and debug them.

Lint every screen and query in the app.

Every save is kept and can be restored. Edits to shared templates are blocked.

A wizard to create an app and connect PostgreSQL or SQL Server.

Link and edit a custom front end's code, with its git history.

Install and stay up to date automatically.

Talk to TAFI with on-device speech input.

Describe what you want; TAFI answers, plans, or builds.

Nothing changes until you say yes, and every change is read back afterwards.

Every change is recorded against the user who approved it.

Requirements → data model → plan → build → verify, with approval gates.

Use TAF's build tools from your own AI assistant.

Use your own AI account; your provider bills you directly.

TAFI answers from a library of verified platform documents.

TAFI helps find why something failed.

Create a new app from conversation.

Each service ships as a container image.

The platform runs on Docker Swarm.

Every request can be traced across services.

We run our own project management on TechAppForce with no bespoke back-end code, and a pilot app runs on a custom front end.

Example apps to start from.