Fully Managed Leantime
as a Service

Creative work runs on retainers, NDAs, and asset versioning. Agencies bound by per-client confidentiality terms — and by DMCA safe-harbor record-keeping for the work they publish — need project history that lives where the agency can find it years later, not on a SaaS account someone closed.

DANIAN's typical creative-agency configuration: a dedicated single-tenant instance, OIDC tied to the agency's Google Workspace. Pick the region closest to the client base — Germany, UK, USA, or Singapore are typical for agency workloads.

A typical workflow: one Leantime project per client engagement, kanban stages from Brief → Concept → Review → Delivery, Whiteboards plugin for ideation, file attachments per ticket for asset versions, time tracking against negotiated rate cards. Project history and file attachments retained for 7 years post-engagement, aligned to standard NDA-retention windows.

Consultancies live or die on time-tracking accuracy, sprint discipline, and the record-keeping that lets a contractor IP-assignment hold up. Clients on regulated work flow security policies down into the SOW — instance access controls, change-history retention, encrypted backups — and the consultancy has to prove all of it.

DANIAN's typical consultancy configuration: OIDC SSO via Authentik or Keycloak (Leantime supports OIDC natively), IP-allowlist on the admin URL, daily encrypted database snapshots with 30-day retention extendable to a year on request.

A typical workflow: GitHub-issue-to-Leantime-ticket sync via the JSON-RPC API, sprint planning via Milestones, weekly status reports via Leantime's Status Update feature emailed to client stakeholders. Access-log entries retained 365 days minimum; backup RPO under 24 hours. The dashboard shows the consultancy what the auditor will ask for.

Coaching and therapy-adjacent practices need client-record retention measured in years, jurisdictional control over where session notes are stored, and a vendor relationship that won't suddenly change terms. AGPL self-hosted Leantime, run by us, gives the practice the second part of that without losing the first.

DANIAN's typical practice configuration: region-locked single-tenant instance, TLS 1.2+ enforced on the edge, encrypted database volume, SMTP via TLS-only relay for client reminder emails. Multi-instance isolation for practices that need to keep coaching engagements separate from supervision groups.

A typical workflow: one Leantime project per client, treatment goals mapped to Milestones, session notes in the per-project Notes feature (visible only to the assigned therapist), recurring tasks for check-in cadence. Client-engagement records retained for the 6 to 10 years required by most jurisdictional health-records statutes.

Non-profits balance grant-cycle reporting against budget pressure, donor-data confidentiality against the need to actually use the data, and program-management software against the reality that most board members aren't going to learn Jira. Leantime's strategy-and-execution-in-one-place model is unusually well-fitted to grant-funded program portfolios.

DANIAN's typical non-profit configuration: cost-optimized shared CPU tier (non-profits are price-sensitive and €9 fits a small line item), region chosen to match the country of incorporation, OIDC tied to Microsoft 365 Business, LDAP-friendly user provisioning for member-organization access.

A typical workflow: the Programs view for grant-funded program portfolios, Milestones aligned to grant deliverable deadlines, automated Status Reports emailed to grantor contacts. Grant-cycle project history retained for 7 years to satisfy federal grant audit requirements or charity-regulator inspection windows.