How Aurachain Was Built

Aurachain v3.0 shipped in April 2019 as the first fully usable release of the platform. Three and a half years later, at v3.13, it had become a platform regulated institutions could run their operations on.

The path runs in four movements. The foundation came first. Then control: who can do what, and proof of what happened. Then reach: mobile, external databases, end users signing themselves up. And finally the obligations that come with regulated work.

v3.0 – The foundation

April 2019

The first production release. A new interface, an application builder rebuilt from scratch, a microservice architecture for cloud and on-premise, and a visual designer for smart contracts.

v3.6 – Control over who does what

March 2020

Granular permissions arrived and reshaped the platform, with 15 default permission sets and per-module rights. The Document Designer was rebuilt, rules became testable, and the platform went responsive on mobile.

v3.7 – One login, one timeline

May 2020

SAML single sign on, tested against Azure, Google, Office 365 and Okta. The Process Inspector timeline deepened, auditing every save with the old value kept beside the new one. Managers gained access to their team’s tasks from a phone.

v3.7.2 – Building things once

July 2020

Fragments let teams maintain a bundle of interface elements centrally and reuse it everywhere. Deadline and expiration behavior was redesigned into a single place, and tenant admins could create users in bulk.

v3.8 – Room for more than one organization

September 2020

Multi-tenancy let several tenants share an environment with data segregated at schema level. The blockchain module was rebuilt around multiple smart contracts per application, and the Data Grid component arrived in the UI Builder.

v3.9 – Work that keeps moving

November 2020

The Reports area was rebuilt around saved and shared filters. Delegation let any user re-route their tasks while away, two factor authentication was added, and the Help Centre appeared on every screen.

v3.10 – Reaching outside the platform

February 2021

Applications could now read from databases the organization already ran, starting with Microsoft SQL Server, surfaced as Global Data Model entities. Dynamic task execution gave every assignee on a step their own task.

v3.11 – Letting end users in

May 2021

Customers of your applications could enroll themselves, through system APIs and a public sign-up route. Oracle and MySQL joined the database connectors, and a new component captured images and video for identity checks.

v3.12 – Meeting the standards

September 2021

SSL certificate management opened up APIs secured with self-signed certificates. Accessibility arrived to WCAG 2.1 with a high contrast mode, and document headers and footers became dynamic.

v3.13 – Proof and erasure

November 2022

GDPR tooling let admins honor a right to be forgotten, deleting an instance or parts of one, archived records included. The Advanced Logic activity brought JavaScript to process level, and the Global Data Model gained import, export and full audit of every structure change.

More from Aurachain

More from Aurachain

See all articles

From intelligence
to action.

Build the operating layer for compliance, risk and fraud. Orchestrate what matters. Protect what counts.

Talk to Aurachain
Compliance·Risk·Fraud·Fraud.Watch