SetGet: the scattered tool stack, consolidated into one work OS

Most teams do not have a tooling problem because any one tool is bad. They have one because the work is spread across a dozen of them: chat in one app, documents in another, tasks in a third, a wiki somewhere else, dashboards in a fourth. Every tool is a separate login, a separate permission model, and a separate copy of the same context — and the data sits on as many vendors’ servers as you have tabs open.

One workspace instead of a dozen tabs

SetGet is a work OS: projects and tasks, documents and a wiki, team chat and dashboards in one place. One search reaches across all of it, one permission model governs all of it, and a task can link straight to the doc that specs it and the thread where it was decided — no copy-paste between tools, no “which app was that in?”

Projects and tasks where the work already lives

Plan on boards, lists or a timeline; assign, comment and track without leaving the workspace. Because tasks live next to the documents and conversations they come from, status is something the system can show you rather than something a person has to assemble from four other tools every Friday.

Docs, wiki and chat next to the execution

Knowledge belongs where the work happens, not in a separate silo nobody opens. SetGet keeps documents and a team wiki in the same workspace as the projects they describe, with chat and threads attached to the work itself. Dashboards roll the whole thing up so you can see where a project actually stands.

• Project and task tracking — boards, lists, timelines
• Documents and a team wiki
• Team chat and threads, attached to the work
• Dashboards and reporting
• Files and assets
• One search across all of it

Self-host it, and keep your data inside your perimeter

SetGet runs as SaaS, but it can also be self-hosted or run in an isolated deployment. Authentication goes through your own SSO (SAML/OIDC), access is role-based, and every change is written to an audit trail. For teams under Türkiye’s KVKK, that means the workspace — and all the project data, documents and conversations inside it — never has to leave a perimeter you control.

One workspace, one permission model, one place your data lives.

Built on the same platform as everything else

The AI inside SetGet — search, summaries and agents that act across your projects and docs — runs on Arpanet’s own in-house model families through the Qevron gateway. Our models, our gateway: the assistance is part of the same sovereign stack as the rest of the platform, not a third-party model quietly reading your workspace from outside.

Consolidation usually means handing more of your work to one external vendor. SetGet is the opposite trade: fewer tools and one workspace, with the option to keep the whole thing — data, identity and the AI on top — inside your own environment. Pricing depends on your deployment and scale; contact us and we will scope it with you.