AtroCore is an open-source platform for the business applications that standard software does not cover. Instead of starting from an empty repository, you configure your entities, fields, relations, layouts, user roles and workflows directly in the admin interface, and write code only for the logic that is genuinely specific to your business. What you get is a working application with its own data model, user management, import and export, REST API and audit trail, built around your processes rather than around someone else's product assumptions.
Business Logic and Automation
- Configurable Workflows and Status Transitions
- Approvals, Reviews and Escalations
- Action Buttons on Records and Selections
- Automatic Field Updates
- Calculated and Derived Values
- Validation Rules and Data Quality Checks
- Scheduled Jobs and Background Queues
- E-Mail and In-App Notifications
- Mass Actions and Bulk Editing
- Document Generation from Templates
- Complete Change History per Record
Integration and Data Exchange
- REST API for All Entities and Fields
- Configurable Import and Export Feeds
- Field Mapping and Value Transformation
- Scheduled and Event-based Data Exchange
- Webhooks for Outgoing Events
- Connectors for ERP, Shop and CMS Systems
- Channel and Marketplace Feeds
- Data Consolidation from Several Sources
- Matching and Deduplication
- Import Logs and Error Handling
- File Transfer via FTP, SFTP and HTTP
Users, Roles and Access Control
- Configurable Roles and Permission Profiles
- Record-level Access via Ownership and Teams
- Field-level Read-only and Hidden Fields
- Role-dependent Layouts and Menus
- Restricted Views for External Participants
- Supplier and Dealer Access to the Same System
- Teams, Assignment and Responsibilities
- Comments, Mentions and Record Following
- Personal Dashboards and Saved Filters
- Multi-language User Interface
- Audit Log of All Changes
Development process with AtroCore
AtroCore shortens the part of the project that normally takes the longest. Data model, interfaces, permission system, automation and notifications are configured in the administration area, so a running application exists early and you review real screens with real data instead of mockups. Development effort goes into the logic that is genuinely specific to your business.
1. Kickoff and concept
In a kickoff meeting we work through your processes and the data behind them. The result is a concept that states which parts of the application AtroCore covers by configuration and which parts require custom development, together with an offer you can plan with.
2. Data model
Your entities, fields, relations and hierarchies are configured in the administration interface. Field types cover text, numbers, dates, currencies, files, links, multi-language values and calculated values, and validation rules are defined per field. The database schema follows automatically, without hand-written migrations.
3. Layouts and views
For each entity you define list views, detail views, search filters, kanban and calendar views, and arrange fields into panels and tabs. Layouts can differ by role, so purchasing and quality assurance open the same record and see the fields relevant to them.
4. Action buttons
Operations your users need are placed directly where they work, as buttons on a record or on a selection of records. A button can start an export, generate a document, hand a record over to another system or trigger a workflow, without anyone leaving the screen.
5. Roles and permissions
Access is controlled per role down to individual records and fields: who may read, create, edit and delete, whether access depends on ownership or team membership, and which fields remain read-only or hidden. External participants such as suppliers or dealers receive their own restricted view of the same system, and every change is recorded in the audit log.
6. Workflows and notifications
Business rules are configured instead of coded: status transitions, approvals, escalations, automatic field updates and scheduled jobs. Users are informed by email and in-app notifications, data is exchanged through configurable import and export profiles, and other systems are connected via the REST API, webhooks and integration modules.
7. Custom development where configuration ends
Requirements that go beyond configuration are implemented as modules within a documented extension architecture, so your specific logic stays separate from the platform and updates remain possible. Developer time goes into your domain logic rather than into user management, import routines or a permission system.
8. Approval and go-live
Each sprint result is tested manually and automatically, then presented to you for approval before it reaches the productive system. Adjustments and extensions go into the next sprint. We train your users, hand over the documentation and support the operation after go-live on request.
Interested?