# “Composable Backend Framework for Custom

# Enterprise Platforms.”

# The Engine Behind Purpose-Built Business Platforms.

---

| CONTENT | Page no. |
| --- | --- |
| Cover | Page 1 |
| Index | Page 2 |
| ATUM is | Page 3 |
| Architecture | Page 4 |
| Integration & extensibility | Page 5 |
| Stack overview | Page 5 |
| Customization scope | Page 6 |
| Security, compliance&audit | Page 6 |
| Deployment models | Page 7 |
| Tested&proven in | Page 8 |
| Ideal use cases | Page 8 |
| Summary | Page 9 |

---

# ATUM is

### ATUM is a modular, workflow-centric backend framework designed to power

complex, domain-specific platforms through customizable microservices. Developed by AtenTEC using the Go programming language, ATUM separates core **business logic from project-specific workflows —** enabling rapid delivery of deeply customized enterprise solutions. Unlike traditional ERPs or rigid SaaS backends, ATUM focuses on **modularity, composability, and integration readiness, allowing teams to build** precision-engineered platforms like FleetFix, Anchor MMS, and others — with full control over operational behavior.

_“ATUM is not an ERP — it’s the_ _modular, workflow-driven_ _architecture that powers our_ _enterprise solutions.”_

## BUILT WITH MICROSERVICES, DEFINED BY BUSINESS LOGIC, AND CUSTOMIZED

## THROUGH DECLARATIVE WORKFLOWS, ATUM ADAPTS TO YOUR OPERATIONS,

## NOT THE OTHER WAY AROUND.

[] Custom-Built Platforms for Complex Operations and Specialized Workflows. **Powered by ATUM.**

---

# ARCHITECTURE

#### ATUM uses a two-layer architecture for every functional module:

#### 1. Core Modules  2. Workflow Layer

- Written in Go • Defines business-specific behavior:
- Provides generic business logic- Custom fields, validation, (e.g., Ledger, Inventory, automation Procurement)- Print formats (via AtenRP)
- Exposes core APIs for CRUD,- Ledger mappings (via LedgerRules) listing, filtering, and system-level • Triggers, notifications, side-effects logic (validation, constraints). • Fully declarative, per-project
- Cannot operate independently • Customizable without affecting the without a Workflow Layer core module layer

#### This separation allows:

Reuse of core logic across verticals

Per-deployment customization

Faster QA and delivery cycles

# ATUM

#### WORKFLOW LAYER

Pre-Project customization logic

**DOCUMENT WORKFLOW** **CUSTOM LEDGER** **TEMPLATES TRIGGERS &** **BUSINESS RULES** (Via AtenRP) **RULES** **NOTIFICATIONS**

### TWO-LAYER ARCHITECTURE

#### WORKFLOW LAYER

Pre-Project customization logic

**LEDGER INVENTORY PROCUREMENT** **ATENRP** (Document Generator)

[] Custom-Built Platforms for Complex Operations and Specialized Workflows. **Powered by ATUM.**

---

## INTEGRATION & EXTENSIBILITY  
[]

ATUM uses a two-layer architecture for every functional module:

| Feature | Description |
| --- | --- |
| APIs | All services expose RESTful APIs. |
| Message Queue | Uses RabbitMQ (Kafka optional) for async workflows. |
| Document Generation | AtenRP engine defines custom outputs(PDF/Excel). |
| Ledger Rules | Declarative accounting impact engine. |
| External Auth Support | Auth is handled by the overall platform not ATUM itself. |
| 3rd Party Systems | Easily connects to payment gateways,ERPs,and more. |

## STACK OVERVIEW

Backend

• Go (Golang)
• AtenGAPI Runtime (Gen 4.40)
• AtenRP (for document rendering)

Infrastructure

• Docker containers
• RabbitMQ (default MQ)
• TLS + scoped tokens

[ ] Custom-Built Platforms for Complex Operations and Specialized Workflows.
Powered by ATUM.

[]

---

# CUSTOMIZATION SCOPE
[]

ATUM uses a two-layer architecture for every functional module:

LAYER

ACCESS BY 3RD PARTY

Core Microservices

No

Workflow Layer (rules)

Yes

Controlled Access

Print Definitions (AtenRP)

Yes

With Templates

LedgerRules Definitions

Yes

Under NDA

UI Layer (Frontend)

Yes

Per Project

# SECURITY, COMPLIANCE & AUDIT

[]

• Scoped access tokens and route-level control

• TLS-encrypted communication

• supports compliance requirements such as:

• GDPR (Europe)

• NCA/SAMA (KSA — via deployment-specific controls)

controls the core runtime, modules, and service engine.

External developers may only extend via approved configuration interfaces.

• ISO 27001-ready environments (when deployed on certified infra)

[]

---

# DEPLOYMENT MODELS

ATUM can be deployed in multiple environments depending on project requirements:

| ENVIRONMENT | SUPPORTED |
| --- | --- |
| On-Prem | Yes |
| Cloud | Yes |
| Hybrid | Yes |

## MINIMUM REQUIREMENTS:

• Docker
• SQL-compatible database
• NoSQL storage (MongoDB or Datastore)
• Message Queue (RabbitMQ)
• External Auth System

ATUM Flexibility –
Multiple Deployment Models

Cloud Deployment

[]

Google Cloud, AWS

Full Data Control

ATUM Deployment Models

---

# TESTED & PROVEN IN

1. FleetFix:
   Car rental

Car rental workshop management.

2. Anchor MMS:
   Marina operation

Enterprises with unique workflows that standard ERP can’t handle.

3. Anchornize:
   Water sports & asset scheduling platform.

All the above use ATUM for:

Governmentbacked digital transformation platforms.

Accounting

Inventory

Notifications

SaaS platforms built for specific verticals (e.g., mobility, maritime).

# IDEAL USE CASES

Companies needing modular infrastructure that grows with their operations.

---

# SUMMARY

ATUM is not a product — it’s a platform to build products.

By separating logic from customization, and exposing flexible interfaces to integrate with any stack, ATUM offers both engineering power and business agility.

For high-stakes enterprise software, ATUM is your foundation.

BUILT TO INTEGRATE EASILY WITH BOTH INTERNAL AND EXTERNAL SYSTEMS.

---

# GET IN TOUCH

## [https://www.atentec.com/atum](/content/atum/index.html)  
+20 69 377 9669

## [info@atentec.com](mailto:info@atentec.com)  
+20 155 234 5445

[] Custom-Built Platforms for Complex Operations and Specialized Workflows. **Powered by ATUM.**