TechAppForceThe platform
Applications as metadata. Run by one platform.
Build in the web app, TAF Studio or TAFI. One engine runs what you configure. No generated code to maintain.
- The web appConfigure in the browser
- TAF StudioThe desktop IDE
- TAFIAI builder, you confirm
- Entities
- Screens
- Lifecycles
- Approvals
- Workflows
- Access rules
- Scripts
The problem
Stop building everything from scratch.
Every product needs these before its first paid feature. On TechAppForce they are already built.
- Built inSign-in
- Built inRoles
- Built inRecord screens
- Built inApproval chain
- Built inEmail reminders
- Built inAudit trail
- Built inReport exports
- Built inShip changes safely
How we solve it
Your application should be configurable. Not hardcoded.
Configuration for the common work. Real code for what makes you different, in the same app.
- Entities, fields, lookups and custom fields
- Lists, forms, dashboards and the components on them
- Statuses, transitions, approvals and SLA rules
- Workflows on record events and schedules
- Reports, exports and scheduled delivery
- Roles and what each can see and change
Change a field or a rule in one place. It shows up on the form, the list and the API.
- Validation and calculation rules too specific for configuration, as C# record hooks
- Screen behaviour the standard components do not cover, as TypeScript screen extensions in the web app
- Custom workflow actions for your own business logic
- Your own versioned API endpoints, with an OpenAPI spec and a generated typed client
- A fully bespoke Angular or React front end on the client SDKs, when the standard screens are not the product
C# scripts are compiled and checked on the platform before they run.
How you work
Six steps from idea to release
The same order in the web app, TAF Studio or TAFI. Nothing reaches users until you release it.
- Define the dataEntities, fields, lookups
- Design the screensLists, forms, dashboards
- Set lifecycle and approvalsStatuses, approvers, deadlines
- Automate with workflowsOn events or a schedule
- Add reportsExport and email on schedule
- Release itYou review the diff first
Enterprise-ready
Ready for your IT, security and procurement review
The questions a larger organisation asks before it commits, answered plainly.
- Access by role and by rowEach role gets its own read, create, update and delete scope per record type. Every record keeps a history of who changed what.Access and identity
- Development, QA and ProductionSeparate environments for every app. Compare every difference, then move changes on as a reviewed release.Environments and releases
- PostgreSQL or SQL ServerYour records live in a database your team already knows. Each environment can have its own database.Architecture
- A standard, familiar stack.NET services, an Angular front end and versioned REST APIs documented with OpenAPI.API reference
- A paid pilot, success criteria in writingStart on your real use case with a fixed scope, working directly with the team that builds the platform.Pricing and pilots
- Your security questionnaire, answeredSend us your questionnaire and we answer it in writing, including what is still on the roadmap.Security
Build the application. Keep the code.
See how TechAppForce combines metadata-driven development, a professional IDE and governed AI-assisted building. When you are ready to build, open TechAppForce at techappforce.io.