Custom software development for companies
T-NEX develops business applications and extends existing systems, from clickable prototypes and integrations to agreed handover and support.
Explore serviceHosting and operations for companies
Reliable support for your software in operation.
T-NEX sets up your application's operating environment and handles the agreed tasks for updates, backups and support. Responsibilities and running costs are clarified from the start. The scope grows with your software's requirements.
Business applicationsYour workflowsInterfaces
Shared data modelData · Roles · Permissions
AI FoundationAI functions within the application
Platform principle; the specific scope is agreed for each project.
In daily work
How to use the solution.
For SMEs, startups and industrial companies with web applications, portals, workflow software or AI solutions.
Operating plans start during development. Accounts, responsibilities and the route from an approved change into the application are established before employees or customers begin using it.
Overview
Use your own accounts or arrange infrastructure through T-NEX
You can hold infrastructure accounts and receive provider invoices directly. T-NEX receives the access required for setup and support. Alternatively, organising the agreed infrastructure can be part of the operating engagement. Technical tasks, account ownership and billing are explicitly defined for either model.
Owning a cloud account does not establish who checks backups or fixes a fault. We therefore record responsibilities independently of the account model. Your company names a contact for business decisions and approvals.
| Model | What your company holds | What is agreed beforehand |
|---|---|---|
| Client account | Infrastructure accounts and direct provider billing | T-NEX access, setup and ongoing support |
| Arranged operations | The usage and handover rights agreed in the contract | Contracting parties, infrastructure scope, billing and operating tasks |
Overview
What does your application need day to day?
An internal knowledge search has different needs from an ordering portal or an application handling large numbers of files. We identify the application, database, file storage and connected services. We also consider user groups, typical traffic, important operating hours and the consequences of an outage.
For AI solutions, we review model calls too: which content leaves the application, how often is a model needed, and what should happen if an interface is unavailable? These answers help establish whether an external service, local processing or additional computing capacity fits the task.
Overview
Assign maintenance, monitoring and recovery
The agreed scope may include software and dependency updates, certificate upkeep, monitoring, backups and incident handling. Each task identifies the affected components, responsible person and information your team receives. An error notification needs a recipient and a defined next step.
For backups, we establish the data covered, retention and how restoration will be checked. For changes, we agree the test environment, approval and a recovery route if problems occur. Required response times, support hours and recovery objectives are defined around your business requirements.
- Which events should trigger a notification?
- Who assesses an incident and informs affected users?
- Which changes need business approval?
- How is it established that a backup can be restored?
Overview
Understand ongoing costs and plan capacity changes
Initial setup, infrastructure consumption and ongoing support are separate cost components. An AI application may add model calls; a portal may need file storage or an email service. The proposal identifies the components required for your project.
We plan capacity around the system and expected workload. If usage or data volumes grow, the required change and its effect on ongoing costs are discussed. Actual usage patterns are more useful for that decision than simply choosing a large server tier.
Overview
Establish data locations and access before setup
The operating picture includes storage locations for the application and backups, along with connected services. It also identifies the people and organisations that can access data for support or development. We describe the intended processing to support the technical and contractual review of your project.
Your requirements determine which content an AI model may receive and which data should be limited before a call. Permissions and the use of production data in development and testing are defined for the workflow. Existing data protection documentation needs to match the processing actually selected.
Overview
Start with a usable operating and handover plan
Before launch, we bring together the system overview, responsible people, required accounts and agreed operating tasks. Your team receives the overview of changes, incidents and handovers defined for the engagement. Business acceptance and technical deployment are coordinated.
A future transition needs preparation: which data can be exported, which access will be transferred, and what documentation does the next operator need? Source code, licences and rights follow the agreed engagement. The handover plan identifies the actual steps and remaining dependencies.
| Document | Purpose |
|---|---|
| System and service overview | Identify dependencies and ongoing costs |
| Task and contact overview | Assign maintenance, notifications and decisions |
| Release and recovery procedure | Handle changes and faults consistently |
| Export and handover plan | Prepare continued operation and a possible provider change |
The workflow
How we introduce the solution.
- 01
Identify the application, data and important operating hours.
- 02
Define account ownership and your team’s tasks.
- 03
Agree resources, costs and support scope.
- 04
Set up the environment and check the agreed operating procedures.
- 05
Hand over the application with documentation and named contacts.
What needs to be agreed before use
Support hours, response times, availability and recovery objectives are agreed for the specific application. Selecting a cloud provider does not establish these services automatically.
FAQ
Questions about the solution
Can we use our own cloud accounts?
Yes. Under the client-account model, you hold the accounts and receive provider invoices directly. Before setup, we define the access T-NEX receives and the ongoing tasks we take on.
Can T-NEX provide support after development?
Ongoing support can be agreed with the development engagement or as a separate scope. We identify the components, maintenance tasks and incident-reporting route. Changes to business functionality are agreed separately.
Are backups and monitoring always included?
They can be part of the operating engagement. The relevant details are the data covered, retention, restoration checks and monitored components. These points and the handling of notifications are explicitly defined.
What determines the ongoing cost of an AI application?
Required infrastructure, data volumes, usage and support. External models add calls and processed content; other services may have their own costs. The proposal separates setup, ongoing infrastructure and support.
Can the software run in our existing environment?
We assess compatibility with the application, available databases, interfaces, permissions and maintenance arrangements. If the environment fits, deployment there can be planned. Differences from the intended system setup are addressed before implementation.
How can we move to another operator later?
We plan the exports, accounts, documentation and transition steps needed for your application. Included source-code and usage rights follow the agreed engagement. A handover test can establish whether the planned documentation and access are sufficient.
Related options
You may also be interested in these.
An AI pilot with defined evaluation criteria
Evaluate one AI use case with T-NEX: limited scope, suitable data and agreed criteria for expansion or stopping.
Explore serviceOutsourcing software development
Commission external software development with clear goals, data responsibilities, roles, acceptance criteria, handover and ongoing operational support.
First version: Updated:
Read articleData protection and hosting
Establish contracting parties, data flows, model access and operating tasks for your application, with additional information on this website’s privacy.
Learn moreWhich task would you like to solve next?
Bring a concrete task. Together, we will define what the application needs to do.
Discuss operations for your application