https://handbook.unicis.tech/ 2026-06-01T20:31:57+00:00 https://handbook.unicis.tech/ https://handbook.unicis.tech/_media/wiki/logo.png text/html 2025-03-16T22:32:35+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/communications?rev=1742164355&do=diff Communications This page explains what every team member (Unicians) needs to know in order to effectively contribute at Unicis. All hands Unicis organizes a meeting called the “All hands” every month. All team members, both internal and external, are required to attend the monthly “All Hands” meeting. All meetings are recorded and team members who can’t attend should watch the recording within a few days. text/html 2024-09-28T13:02:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/leadership?rev=1727528527&do=diff Leadership This page contains information that managers and other leaders at Unicis should know about running a great company. CEO Flaws Openness is important, and I want to share the flaws I have setup with you. I am fully accountable for enhancing the items listed below, and listing them is not an excuse. text/html 2024-09-25T12:26:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/products?rev=1727267202&do=diff Products This page covers the things every team member needs to know in order to effectively contribute at Unicis. Product roadmap The Unicis product roadmap is transparent and can be found via the Unicis Feedback portal. However, strategy and priority information is handled internally on a Strategic Level and later reflected in the internal GitLab repository and on the Feedback portal. text/html 2026-05-19T17:23:59+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/development/release?rev=1779211439&do=diff Releasing Warning This page is still in progress and may require refinement. Versioning Scheme The Unicis Platform uses Calendar Versioning (CalVer): * Major/Minor releases: vYYYY-MM (e.g. v2026-05) * Patch releases: vYYYY-MM-DD (e.g. v2026-05-12) Release branches follow: text/html 2026-05-25T06:08:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/platform_release?rev=1779689296&do=diff Platform Release ← Back to Core Processes ---------- Purpose To ship Unicis Platform releases consistently, with clear quality gates, predictable communication, and no surprises for customers or the community. Owner Peter Zlatev — CTO Trigger This process starts when the team agrees a set of features/fixes is ready to ship — either at the end of a planned sprint or when a critical fix requires an unplanned release. text/html 2025-07-14T13:49:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/trust_center/processes_and_procedures?rev=1752500981&do=diff Processes and Procedures 1. Introduction The processes and procedures essential for the efficient operation of Unicis are described in this document. It is designed to keep employees and the open-source community connected and productive. 2. Onboarding Process text/html 2024-09-29T10:42:59+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/development?rev=1727606579&do=diff Introduction to Development At Unicis, our development process is the backbone of creating secure and compliant solutions. This section outlines our methodology, team structure, and best practices to ensure our products meet the highest standards. Development Philosophy and Approach text/html 2024-11-26T16:00:23+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/soc?rev=1732636823&do=diff Unicis SOC Plan Comprehensive breakdown of features and integrations for UNICIS SOC stack that includes Wazuh, TheHive, Zabbix, MISP, Cortex, and Shuffle SOAR. Integrated Features 1. Centralised Incident Management * Wazuh + TheHive: * Automate alert ingestion from Wazuh into TheHive to create structured cases. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/scorecard?rev=1779688593&do=diff Scorecard The Scorecard gives every Unician a weekly pulse on the health of the business. It replaces gut-feel with objective numbers. Every metric has a single owner — not a team, one person — and a weekly target. The Scorecard is reviewed in the first 5 minutes of every text/html 2024-10-05T13:04:21+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/development/devops?rev=1728133461&do=diff DevOps Introduction Welcome to the Unicis DevOps Handbook. This guide is designed to help you understand and manage the DevOps processes for the Unicis Platform, which is built on Platform-as-a-Service (PaaS) infrastructure using OVH Cloud and utilizes CapRover for Continuous Integration and Continuous Deployment (CI/CD). text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/customer_onboarding?rev=1779688593&do=diff Customer Onboarding ← Back to Core Processes ---------- Purpose To take a new trial signup from first contact to an active, value-realising customer — consistently, within 14 days of signup. Owner Predrag Tasevski — CEO / Visionary Trigger This process starts when a new trial signup is confirmed — either via the unicis.tech signup form (Mautic notification) or via a direct outreach that results in a trial account being created. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/start?rev=1779688593&do=diff Core Processes This section documents the Core Processes that run Unicis. A Core Process is a named, repeatable workflow that produces a consistent result. Every process has a single owner, a clear set of steps, and a list of the tools involved. Documenting processes is not bureaucracy — it is how Unicis delivers consistent quality as the team grows, onboards new Unicians, and operates across time zones. text/html 2024-10-15T09:54:31+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/trust_center/policies/it_security_policy?rev=1728986071&do=diff IT Security Policy Effective date: 17.05.2024. Security is very important to Unicis and everyone here is doing their best to keep your presentations and data secure. This document describes our internal security policies, and minimum security baseline and how those translate into creating a secure platform, add-ons and plugins that you can trust. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/traction?rev=1779688593&do=diff Traction: Rocks, Meetings & Issues Traction is the EOS discipline that turns vision into execution. It is built on three things: Rocks (quarterly priorities), Level 10 Meetings (weekly execution rhythm), and the Issues List (structured problem solving). Without traction, the best strategy stays on paper. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/vision_traction_organizer?rev=1779688593&do=diff Vision/Traction Organizer (V/TO) The V/TO is the single source of truth for where Unicis is going and how we will get there. Every team member should read and understand this document. It is reviewed and updated at every Annual Planning session and checked at every Quarterly session. text/html 2024-09-25T12:27:31+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/development/environments?rev=1727267251&do=diff Environments Each of these environments is important in the software development life cycle. Changes are tested and validated before they reach end-users in the Production environment, where stability and reliability are important. Development Environment text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/process_template?rev=1779688593&do=diff Process Template Copy this page when creating a new Core Process. Replace all placeholder text in [brackets]. ← Back to Core Processes ---------- [Process Name] Purpose [Why does this process exist? What problem does it solve? One or two sentences.] Owner [Full name] text/html 2025-07-14T15:47:56+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/recruitment?rev=1752508076&do=diff Recruitment To keep up with technology changes and new technologies, we aim to expend our team into a strong and quality people, where we can build a community and a company. How we hire At Unicis, we work with core team members, consultants, advisors, and people in the community. text/html 2025-06-04T05:04:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/company/unicis?rev=1749013478&do=diff Unicis.Tech Purpose Unicis is an open-core company that sells applications via the Atlassian Marketplace and subscriptions for all-in-one SaaS products. Today, Unicis helps startups get certified and compliant with international standards, frameworks, and benchmarks. Unicis is committed to a comprehensive strategy against, whatever it may be. text/html 2026-05-25T06:10:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/eu_project_delivery?rev=1779689443&do=diff EU Project Delivery ← Back to Core Processes ---------- Purpose To deliver EU-funded project obligations (deliverables, milestones, reporting) on time, with clear internal ownership, and without disrupting core platform work. Owner Predrag Tasevski — Stakeholder & EU Projects Management text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/invoicing_billing?rev=1779688593&do=diff Invoicing & Billing " 🔄 Status: Draft — Will be updated when billing.unicis.tech is live." ← Back to Core Processes ---------- Purpose To issue invoices accurately, collect payment reliably, and maintain clean financial records — for customers, partners, and EU project claims. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/partner_onboarding?rev=1779688593&do=diff Partner Onboarding " 🔄 Status: Draft — This process is defined but not yet fully operational. billing.unicis.tech and the partner programme are in development. Update this page when the partner programme launches." ← Back to Core Processes ---------- Purpose To onboard new reseller, integration, or referral partners into the Unicis partner programme — from first contact to active, contracted, and billing-enabled partner. text/html 2026-05-25T06:13:52+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/support_resolution?rev=1779689632&do=diff Support Resolution " 🔄 Status: Draft — Review and approve at next Quarterly Session." ← Back to Core Processes ---------- Purpose To resolve customer and community support requests consistently, with clear response time expectations and a closed feedback loop. Owner