Engineering HubComing soon · in testing

Bring customer context directly to development.

Collect customer reports, link tickets to issues and prepare context for your development team in a controlled, supervised environment.

  • Technical dossier linked to the ticket
  • Code stays in the customer’s environment
  • Every action is traceable and verifiable
Bring customer context directly to development.

Diagnosis

From customer report to a verifiable diagnosis

Separate evidence, hypotheses, impact and change risk before touching the code.

Engineering details in the ticket

See the identified product, linked Technical Report, session status and collected evidence in the conversation.

Evidence you can verify

Logs, attachments, messages and command results link back to their sources so you can reopen and verify them.

Duplicates and impact

What has already been seen, across how many organisations and with what weight.

Missing data

If something is missing you get a list of questions to put back to the customer.

Runner with no inbound ports

The runner requests work from within your network and needs no inbound connections.

Credentials stay in your environment

Credentials stay where you configured them. The runner sends back events and evidence.

Levels

Decide how far technical assistance can go

Start with analysis and enable further capabilities only when the team is ready. The level can be changed or reduced at any time.

Configuration, availability and frequently asked questions
More about this feature

Collect customer reports, link tickets to issues, and prepare context for your development team. Engineering Hub supports analysis with evidence and assisted tools in a controlled, supervised environment.

  • Technical dossier linked to the ticket
  • Code stays in the customer’s environment
  • Every action is traceable and verifiable

Coming soon. We’re completing validation before commercial availability.

Levels, permissions and security
L0 · Suggestions
No action. The suggestion appears and nothing else. It lets you see whether it is relevant before it has any effect.
L1 · Issues with confirmation
Create and comment on issues. Linking or opening an issue goes through a human confirmation, every time.
L2 · Analysis
Repository read access. The analysis is produced and read. No writing outside Uppo.
L3 · Local runner
Dependencies, tests and local edits. The change stays on your machine: you look at the diff it produced, it is not pushed anywhere.
L4 · Draft pull request
Branch and draft pull request. The pull request is created as a draft. Review and merge stay with a person.

Secrets stay outside the perimeter. No level grants access to your organisation's secrets: it is not one step further up the same ladder.

Merge and release stay with a person. At no level can Engineering Hub merge or deploy to production: it is not a capability to switch off, it does not exist.

The model

From ticket to issue, without losing context

Connect customer requests, technical analysis and development issues. Customer care and engineering work on the same problem with the information each team needs.

  1. 01

    The ticket

    The conversation with the customer, on the channel it arrived from. It stays the main view for the support team.

  2. 02

    The technical report

    One technical problem, to which many tickets from the customers your team handles — inside your own Uppo workspace — can be linked. This is where the overall impact is read.

  3. 03

    The repository issue

    Either found among the open ones or created. Either way, a person confirms it.

  4. 04

    The session

    The agent’s work, with a status, an owner and a point where it stops. Stopping before the end is an expected outcome.

  5. 05

    The analysis

    The written diagnosis, with what was observed kept apart from what was inferred.

  6. 06

    The evidence

    Reproduction and tests, with the attachments that back them up. A result that is missing is recorded as missing.

  7. 07

    The draft pull request

    At the top of the ladder, and always as a draft. Review, merge and release stay with a person.

Every step keeps who decided, on what grounds and with how much confidence: that is what lets you reread a decision weeks later.

It is not Uppo Flow, and it is not an automation

Flow runs an internal procedure made of assigned steps and approvals; automations react to an event on a ticket. Engineering Hub does a third thing: it carries a customer problem into the engineering work, and carries the answer back.

See how Uppo workflows work

Deduplication and impact

Merge duplicates and measure real impact

Group several tickets under the same technical problem and show how many organisations are affected, for how long and with what priority.

See what the GitHub connector exchanges
Where the work happens

Customer care and engineering work from the same context

Support stays in the ticket; engineering receives a linked technical brief without reconstructing the story from scattered messages.

The Engineering panel in the ticket

Recognised product, linked technical report, issue, session status and collected evidence. From here you confirm the product and link the issue without leaving the conversation.

The agent console

Enrolling and revoking runners, the organisation's level, spending caps and a stop switch. These are administrator actions and live in a separate panel.

Every action stays linked to the ticket and the session it came from: whoever reads it later finds the context alongside the result.

Make it work for your team

Evidence and hypotheses

Evidence

Logs, attachments, ticket messages, results of commands that were actually run. It has a source you can reopen and check.

Inference

Hypotheses about the cause, likely files, correlations. They are marked as such, and stay hypotheses even when they are well written.

When the material is not enough, the analysis asks for what is missing instead of guessing a cause.

The code stays in your own environment
Execution

The code stays in your own environment

Analysis runs in your own environment. Use Uppo to define the scope, track progress and manage permissions.

No network port to open

The runner exposes no ports and receives no requests: it asks for work. It installs inside a corporate network without opening anything inbound.

An isolated workspace

Every run gets its own directory. The repository copy and the toolchain stay on your machine.

Only the commands you allowed

Only listed commands are run, without going through a shell and without inheriting the environment of the process that starts them.

Enable and revoke from the console

A runner is added when you need it and revoked when you don't, from the administrators' panel.

Time, resources and stop

Every run has a time cap. The heartbeat back to Uppo is also the channel that tells a run to stop, and a runner that is down is visible.

Credentials stay where you configured them

With the provider's local authentication, keys never reach Uppo: what comes back are events and evidence, not secrets.

The runner is installed in the environment you choose, with the commands you authorise: you define the perimeter before switching it on.

Levels and permissions
Controls

Every action respects scope, permissions and approvals

The agreed scope, enabled level and approval of each individual action are verified separately.

The programme scope

What has been enabled for your organisation, agreed together with the team.

The level

How far the administrator has raised the ladder. It can be changed from the panel at any time.

The approval

What a person has authorised on that specific session. Installing dependencies or touching code always requires it, on top of the permission.

The level can be lowered at any moment from the console, without waiting for anyone: control stays on your side even once the programme is running.

Configure Engineering Hub for your environment
Configuration

Configure Engineering Hub for your environment

Connect products, repositories, controls and the operating level, starting from a real report from your team.

Who it is for

Teams that build the product they support

If customer reports become issues in your repository and you need context, impact and evidence in one place, the programme is built for you.

How you start

A real case, a controlled scope

Start from the level included in your plan and a real technical case. The scope can grow while keeping explicit approvals and controls.

What we configure

Catalogue, repositories and starting level

Your products, components and repositories, the GitHub connector, the commands allowed on the runner and the starting level: we set them up with your team.

The AI proposes, a person confirms: no action on the repository starts without an explicit authorisation.

Frequently asked questions

The first questions we get from people evaluating Engineering Hub.

What is the difference between a ticket and a technical report?

The ticket is the conversation with one customer. The technical report is the technical problem itself, which many tickets from different customers can be linked to. They serve two different purposes and do not replace each other: the ticket stays the support team's view.

Can I link several tickets to the same issue?

Yes, and that is the normal case. Several tickets feed the same technical report and the same repository issue, and customer impact is read in aggregate. Merging or splitting two groups is recorded with author and date.

Which development tools does it integrate with?

The supported integration is the GitHub connector, which exchanges opening, comments and closing in both directions between Uppo tickets and issues. If you work with another tool, raise it with the team when you join the programme.

Is our code sent to Uppo?

No. Uppo is the control plane: the repository copy, the toolchain and the execution all sit on the runner, in the environment you authorise. What comes back to Uppo are events and evidence of the work done, not the repository.

Which AI providers can I use?

The provider is configurable and you are not tied to a single vendor: it is chosen with the team when access is configured.

Can it change code or open a pull request?

Only at the top levels of the ladder, and only in the environment you authorise: the change stays on your machine and the pull request is created as a draft. Every step requires an explicit authorisation, and review and merge stay with a person.

Can it merge or deploy to production?

No, at no level. Merge and deployment remain outside Engineering Hub: they are not among the capabilities the programme can grant.

How are actions approved?

Programme scope, organisation level and the approval of the individual action are three separate controls, and all of them are checked. Installing dependencies or touching code always requires an explicit authorisation, on top of the person's permission.

How do you protect tickets, attachments and secrets?

Ticket content is treated as untrusted material. Personal data is cleaned before anything leaves for the repository, recognised credentials are refused rather than masked, and every action leaves a trace with author, reason and reference.

How do I get access to Engineering Hub?

Engineering Hub is currently in testing and is not yet commercially available. Access and its final scope will be published after full validation.

How does the operating scope expand?

At launch, the plan will set the available level, while permissions, repositories and approvals will define what can happen in your environment. Every sensitive action will remain under human control.

Routing

Route every report to the right product and repository

Classify product and component using verifiable signals. When context is insufficient, Engineering Hub asks for confirmation.

A catalogue of products and components

Product, component and repository are linked entries in your organisation's catalogue. A name typed into a ticket does not become a routing decision.

Signals you can verify

Inbound channel, form, brand, team, products the customer already uses, and request history. Every signal is stated, so you can see why the suggestion is what it is.

Candidates, with the reason next to them

When there is more than one possibility they arrive in order, each with the reason it was suggested.

Several repositories for one case

A report can involve more than one component: the link is not limited to a single repository.

It asks when the context is not enough

The case waits for a choice instead of being routed to the least-bad candidate just to close it.

The agent has the final word

The choice can be corrected, and the correction is recorded: that is how you later understand where recognition was going wrong.

Read more

Workflows and approvals

Internal procedures with assigned steps, due dates and approvals: a different job from the one Engineering Hub does.

See Uppo Flow

GitHub connector

What an Uppo ticket and a GitHub issue exchange, in which directions, and how it is switched on per company.

See the GitHub integration

All the features

The rest of the platform: tickets, channels, knowledge base, self-service portal and automations.

See the features

Plans and prices

What each Uppo plan includes. Engineering Hub availability will be published after testing is complete.

See the plans

Connect support and engineering

Engineering Hub is coming soon. Tell us how you handle technical issues and let’s discuss your workflow.