Skip to content
FutureCore Technologies, back to top

Built for work that has to be right.

FutureCore Technologies makes secure, accessible software for organisations answerable to regulators, auditors and the public. Every product we build stands on one platform, so sign-in, tenancy, audit and retention are in place before the first feature is written.

Start a conversationWatch the film1:00
Built on
FutureCore Platform
Sign-in
Microsoft Entra ID
Cloud
Microsoft Azure
Accessibility
Built to WCAG 2.2 AA

Two sample products. One core beneath them.

Invoices and Vouchers are sample products, built on the platform to show what it carries. They solve different problems. Drill into either one and you reach the same ground.

Invoices

Every invoice filed, and accounted for.

E-invoicing for the finance and tax teams who have to show what was submitted, when, and what came back. A rejection arrives as a message to a person, with the field to fix.

A replay with synthetic data. Invoices are submitted to the tax authority and acknowledged. When one is refused, a person corrects the one field it names and files it again, and it is accepted on the second attempt.

InvoicesExample organisationSynthetic data
Submissions
Submitted today
Submitted
128
Accepted
127
Awaiting response
0
Need attention
1
Synthetic e-invoice submissions
InvoiceResponseStatus
INV-004820AcknowledgedRef 920E-24Accepted
INV-004819Buyer tax number not registeredCorrect it, then file it againRejected
INV-004818AcknowledgedRef 920C-22Accepted
INV-004817AcknowledgedRef 920B-21Accepted
INV-004816AcknowledgedRef 920A-20Accepted

Vouchers

Every voucher issued, every redemption recorded.

Voucher schemes issued to people by email and redeemed in person, with every issue and every redemption on the record.

A replay with synthetic data. A person opens the voucher emailed to them and shows its code and square on their phone. The counter scans the square, confirms the voucher is valid, redeems it, and the redemption is added to the list of vouchers redeemed today.

Your product

The next product starts on the same core, with every layer below already in place on day one.

  1. Your productReady on day one
  2. Console
  3. Sign-in
  4. Organisations
  5. Roles
  6. Audit trail
  7. Retention
  8. Microsoft Azure
Talk to us about yours

Seven layers every product inherits.

Authentication, tenancy, roles, audit, retention and compliance arrive as platform capability, not as work each product repeats. Delivery effort goes on the problem only your service has.

12.0 m

An accessible console from the first build

Every product opens in the same app shell: estate and organisation consoles, a command palette, keyboard shortcuts, and localisation for any language. The whole service targets WCAG 2.2 AA, mapped to EN 301 549 for UK public sector procurement.

  • Built to WCAG 2.2 AA
  • EN 301 549 V3.2.1
  • Any language

It speaks their language. The same console greets everyone in their own language, with keyboard shortcuts for people who would rather not reach for a mouse.

24.0 m

Sign-in with Microsoft Entra

People sign in with the Microsoft account their organisation already manages. Second factors include Authenticator, passkey, security key, text message and Windows Hello. No product keeps passwords of its own.

  • Microsoft Entra ID
  • Passkey and security key
  • Windows Hello

No new password. People sign in with the work account they already have. The product keeps no password of its own.

36.0 m

Many organisations, one deployment, firm walls

Each product runs as one deployment with many organisations inside it. A tenant can share infrastructure, or be given a database and a storage account of its own. Government and commercial customers never share a deployment.

  • Shared or isolated
  • Own database and storage
  • Separate gov and commercial

Good walls make good neighbours. Many organisations share one deployment, and none of them can wander into another's records.

48.0 m

Access granted per organisation, never assumed

Owners, operators and organisation admins hold the system roles, and each product adds its own, from Auditor to Approver. Every grant is recorded. External systems connect as API clients whose credentials stay in Microsoft Entra.

  • Role-based access
  • Per-organisation grants
  • Entra-held API credentials

Keys for the job, not the building. Each person gets the access their role needs in their own organisation, and every key handed out is written down.

60.0 m

A trail an auditor can follow

Who did what, to which record, and when. Activity is written as it happens and can be read back in the console for one person, one organisation or the whole estate.

  • Every action attributed
  • Person, organisation, estate
  • Read in the console

Every step leaves a footprint. Each action is written down as it happens, so an auditor can follow the trail back, step by step.

72.0 m

Kept as long as the rules say, and no longer

Records are kept for as long as your rules require, with legal holds when a case needs one. A subject access request is answered with one export: everything the deployment holds about one person, as a file you can send them.

  • Configurable retention
  • Legal holds
  • Subject access export

Kept as long as the rules say. Records are deleted when their time is up, unless a legal hold says a case still needs them.

84.0 m

Microsoft Azure, shipped through gates

Hosted on Microsoft Azure: App Service, SQL, Storage, Front Door, Key Vault and Application Insights. Defined in Bicep, and deployed through Azure DevOps pipelines that gate on tests, coverage, security scans and contrast.

  • Microsoft Azure
  • Bicep and Azure DevOps
  • Gated pipelines

Four checks before anything ships. Every release passes tests, coverage, security and contrast checks on its way to Microsoft Azure. Fail one and it stops.

98.0 m

From an empty folder to an audited product.

One minute of the platform at work: a product scaffolded, its layers laid beneath it, a sign-in, a role granted and recorded, a person's data exported on request. The console is the platform's own interface; every name and record in it is synthetic.

  1. 0:00ScaffoldOne command starts a product from the platform template.
  2. 0:08InheritSeven layers arrive beneath it. None are rebuilt.
  3. 0:17Sign inMicrosoft Entra ID and a second factor, from day one.
  4. 0:24OperateA role is granted to one person, in one organisation.
  5. 0:35RecordThe change is on the record, and nobody can edit it.
  6. 0:43AnswerA subject access request, answered with one file.
  7. 0:54The coreBuilt for work that has to be right.
102.0 m

We build the part only you need.

Every engagement runs the same way, and each run leaves more in the ground than the one before it.

  1. Run 1
    104 to 106 m

    Define what has to be right

    We start with the rules your service answers to: the regulator, the auditor, the accessibility standard, and which data it must keep and for how long.

  2. Run 2
    106 to 108 m

    Start on the core

    Your product is scaffolded on the platform. Sign-in, tenancy, roles, audit and retention work from the first build.

  3. Run 3
    108 to 110 m

    Build the service itself

    Delivery time goes on the workflow your staff and your public actually use, shipped through gated pipelines.

  4. Run 4
    110 to 112 m

    Run it on the record

    Hosted on Microsoft Azure, built to WCAG 2.2 AA, with every action on the audit trail.

114.0 m

Tell us what has to be right.

Describe the service, who it answers to, and when it needs to be live. We will come back to you with how it would stand on the core.

Or write to solutions@futurecoredev.co.uk

We use these details only to reply to you. See our privacy notice.

Protected by reCAPTCHA. The Google Privacy Policy and Terms of Service apply.