Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guide iconUser guide
Developer guide iconDeveloper guide
Admin guide iconAdmin guide
English
  • Русский
  • English
Login
    Getting StartedAdministrator documentationFunctional characteristics
      Technology descriptionarrow
    • Architecture OverviewComponent Description
        Deployment schemesarrow
      • Basic schemeFail-safe schemeTypical Placement in Infrastructure
    System requirements
      Admin Panelarrow
      • Account areaarrow
        • Accountsarrow
        • Account UsersAccount Virtual SendersAccount Database Indexes
        TariffsExternal data configurationLDAPTasksSchedule JobsGlobal Stop ListsWebversion Store Policies
        Settingsarrow
      • Databases
          Accessarrow
        • AdminsAPI tokens
        Notifiers
          MTAarrow
        • Default rulesRetry rulesLock rulesBounce patternsStrategiesKeysISPsPools
      Nodes
        Sendersarrow
      • EmailSMSEvent generatorIntegration with Altcraft Cloud SMTPIntegration with Sendsay
        Reportsarrow
      • Audit JournalData Usage
        Toolsarrow
      • ARF decoderURL decoderSMID decoderLicense
      Platform installationarrow
    • Automatic installationManual installationRunning the platform in a Docker container
      Platform configurationarrow
    • Configuration fileDomain settingsLDAP access configurationSending Email via SMTP relayPixel and push domain configurationCluster and Replication SetupSystem notifications configurationProcesses UNIX sockets configurationHTTPS ConfigurationMigrating from MongoDB Community Edition to Percona Server for MongoDBAdding sender IP addressesDeduplication request settingsPostgreSQL database for Market dataProxy server settingsKeycloak Integration with AltcraftGetting HTTP service statusesConfiguring MongoDB log rotation
        Configuration of system constants and directoriesarrow
      • Filtering bot actionsDirectory of gender markers
      Platform maintenancearrow
    • Personnel requirementsPlatform maintenance processesPlatform updatingBackup and recoveryTransferring the platform to a new serverCreating, deleting, and populating tables for statistics in ClickHouseUsing the aktool utilityUsers and directories engaged by the platformPlatform service monitoringProcess and mailing monitoring via Prometheus
      Custom channels guidearrow
    • OverviewCreating and configuring a channelEntity field configurationTemplate languageEntities
        Pipesarrow
      • Pipe: Basic ConceptsResultErrorsLogPackUnpackHTTP RequestStore SetStore GetSelectorSQLEventerScheduler
        Pipelinesarrow
      • Pipeline: Basic ConceptsMessageScheduleListenerModerateStop
      Extraarrow
    • System page customizationSend Message IDClickHouse History Migration GuideInstructions for migrating history to ClickHouseUtility for importing push subscriptions to Firebase projectUtility for importing push subscriptions to Firebase projectENS: настройка интеграции
    Processing HTTP/HTTPS traffic
      Administrator APIarrow
      • Accounts admin apiarrow
        • Restricted accessarrow
        • Account Activation and DeactivationAccount Freeze and Unfreeze
        Get accounts listAdd a new accountDelete the account
        Account usersarrow
      • Update an Existing AccountAdd a new userDelete a userGet a list of usersSending a Welcome Email
        Nodesarrow
      • Synchronize node MTA configurationGet nodes listGet node MTA statusActivate node MTADeactivate node MTA
        Senders admin apiarrow
      • Create or update AKMTA senderGet AKMTA sender informationAssign account to senderGet senders listDelete senderRestore sender
          Sender queuearrow
        • Get sender queue informationHold sender queueRelease sender queueClear sender queue
        Virtual sendersarrow
      • Get virtual senders listGet virtual sender informationCreate virtual senderUpdate virtual senderClone virtual senderDelete virtual sender
    Documentation Archive
  • Platform maintenance
  • Personnel requirements

Personnel requirements

Specialists who maintain Altcraft, administer and support the infrastructure must have the following knowledge and skills:

Mandatory requirements​

  • Technical education;
  • Knowledge of TCP/IP protocols, ability to configure firewalls and diagnose network issues;
  • At least one year of Linux administration experience (Ubuntu/CentOS/Debian);
  • Command-line skills: process management, file permissions, system limits (ulimit, systemd);
  • Knowledge of Altcraft platform functionality (see Architecture Overview and Component Description);

Databases and storage​

The platform administrator works with the following databases and storage systems:

MongoDB​

  • Installation, configuration, running as a systemd service;
  • User and access rights management;
  • Index creation and management;
  • Replica set configuration;
  • Backup and recovery (mongodump/mongorestore);
  • Performance diagnostics (slow query log, profiler);
  • MongoDB is used for Control DB (system settings), FileDB (files and media), and each account's databases (subscribers, campaigns, templates, segments, etc.);

ClickHouse​

  • Installation and basic configuration;
  • User and database management;
  • Understanding table structure and partitions;
  • Backup and recovery;
  • ClickHouse is used for analytics, event history, segmentation, and caching external SQL queries;

Kvrocks (Redis-compatible storage)​

  • Installation, running as a systemd service;
  • Basic redis-cli commands (keys, memory, connections);
  • Backup (RDB/AOF);
  • Kvrocks is used as a system cache, for campaign deduplication, workflow cache, and loyalty program cache;

SSDB​

  • Installation from source code, running as a systemd service;
  • Configuration management (tab indentation in config files);
  • Managing multiple instances (hardbounces, notifications, MTA statistics);
  • SSDB is used for email stop lists, notifications, and hourly statistics;

RabbitMQ​

  • Installation, running as a systemd service;
  • User, vhost, and permissions management (rabbitmqctl);
  • Queue monitoring via web interface (port 15672);
  • Disk free limit configuration;
  • RabbitMQ is the main message broker for communication between all platform services;

PostgreSQL (optional)​

  • Installation and basic administration;
  • PostgreSQL is used for the Market module (products, orders) and as DataDB for accounts;

Web servers and proxies​

  • Nginx — understanding configuration structure, SSL termination, reverse proxy;
  • The platform automatically generates Nginx configurations via akd, but the administrator must be able to diagnose proxy issues;

Object storage (optional)​

  • S3-compatible storage (MinIO, AWS S3, Yandex Cloud Storage, or others) — basic understanding of the S3 protocol (buckets, access, endpoint);
  • Used for storing platform files (attachments, media, import/export);

Platform tools​

  • akd — platform service management: start, stop, restart, status, list;
  • aktool — administrative utility: database migrations, account management, segments, licenses, MTA nodes;
  • Understanding the main.json configuration file structure and ability to make changes;

Monitoring and diagnostics​

  • Prometheus — collecting metrics from platform processes (each service exports metrics on a separate port), Push Gateway configuration;
  • Monitoring key indicators:
    • Disk space (MTA spool, logs, segments, databases);
    • RabbitMQ queues (length, consumption rate);
    • Kvrocks (memory, connections);
    • MongoDB (pool connections, query time);
    • ClickHouse (insert speed, table size);
    • SMTP (delivery, bounce rates, complaints);

Authentication (optional)​

  • LDAP — configuring connection to an LDAP server for admin panel authentication;
  • Keycloak — configuring Keycloak integration for alternative authentication;

Containerization (optional)​

  • Docker / Docker Compose — running the platform in a container, volume management, image updates;
  • The platform is delivered as a monolithic Docker image; databases and brokers are deployed separately;

System utilities​

  • cutycapt + xvfb — HTML email preview generation (headless rendering);
  • Understanding system limits (nofile, memlock) and their impact on performance;
note

Elimination of software errors in the platform operation is carried out only by specialists of Altcraft LLC, after the collected diagnostic information is provided to them.

Last updated on Jul 1, 2026
Previous
Platform maintenance
Next
Platform maintenance processes
  • Mandatory requirements
  • Databases and storage
    • MongoDB
    • ClickHouse
    • Kvrocks (Redis-compatible storage)
    • SSDB
    • RabbitMQ
    • PostgreSQL (optional)
  • Web servers and proxies
  • Object storage (optional)
  • Platform tools
  • Monitoring and diagnostics
  • Authentication (optional)
  • Containerization (optional)
  • System utilities
© 2015 - 2026 Altcraft, LLC. All rights reserved.