AOS is a governance-first platform for associations, foundations, chambers,
exchanges, federations and unions. It goes past the member register: it runs the
meeting → agenda → decision → action chain end to end and makes
the organization's memory answerable.
Set up in minutes · Each organization in its own isolated space ·
Turkish, English, Russian
Why AOS?
Plenty of software keeps a member list. What AOS cares about is
what the organization decided — and what came of it.
The governance chain
A meeting is scheduled, agenda items are worked through, the decision is
numbered (D-2026-014), and the action it creates is tied to a person and a
date. No link is left dangling.
Attendance and absence warnings
Three-state attendance (present / absent / excused), a per-member attendance
rate, and a warning that goes out on its own after two consecutive unexcused
absences.
An institutional memory you can question
Decisions and minutes are indexed automatically. "What did we decide about
this before?" comes back with its sources.
Letterheaded output
The organization's logo is uploaded once and used in three places: the
application shell, the minutes PDF letterhead and email templates.
Permissions and an audit trail
Permissions are granted per operation; every critical change is written to the
audit trail, and the request log shows who tried what.
Three languages
The interface runs in Turkish, English and Russian, so chambers and unions with
international members work from a single installation.
Strategic management
The strategy tree links to goals, goals to KPIs; committee scorecards feed the
management-review report and risks go into a register — the organisation's
long-term plan is tracked in the same place as its daily work.
Inside the product
The three screens that carry the day-to-day work.
The chain is traceable. Which decision each action came from,
and which agenda item and meeting each decision came from, is on the record.
The attendance grid. Attendance rate and absence warning in
one table; members past the threshold are flagged.
Institutional memory. An answer always arrives with the
decision it rests on — you never decide without seeing the source.
Start in three steps
Open your organization
An organization code, a name and the first administrator account. Your
organization opens in its own isolated space; your data never falls into
another organization's query.
Describe your structure
Units, committees, membership types and roles. Invite users or create
accounts directly, and give each role only the permissions it needs.
Run the meeting
Prepare the agenda, mark attendance, number the decision, tie the action to
a person. The minutes come out as a letterheaded PDF.
Your data stays apart
On a multi-tenant platform one question matters most: how is my data kept apart from my neighbour's?
Organization isolation
Every record carries an organization id and every query is bounded by it. Permissions that cross the organization boundary belong to the platform operator alone.
Audit trail
Critical changes are recorded with who and when; separately, the request log shows failed logins and forbidden access attempts.
AI that a human approves
The assistant drafts minutes and recalls past decisions — but never changes a record on its own. A person approves the suggestion.
Data protection
Member consent records, data export and deletion requests are defined inside the product.
