Member Avatar for MCMdizajn

Hello,

I am looking for the Intranet solution for 50 users cca and I was wondering what solutions you can suggest me based on your professional exoperience?
What are the benefits and drawbacks of open source vs commercial solutions for Intranet?

Many thanks in advance and best regards!
Adi

  • 4 Contributors
  • 3 Replies
  • 270 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by marie.talcod

Dani AI

Generated

Practical, compact guidance for a 50-user intranet that builds on points from , and .

Core things to require up front:

  • Single sign‑on (AD/LDAP/SSO) and role-based permissions.
  • Document management (versioning, check-in/out, retention) and reliable full‑text search.
  • Easy admin interface, low training friction, and mobile/browser support.
  • Backups, restore tests, audit/logging and a patching schedule.
  • Integration points (calendar, mail, HR/CRM systems) and exportable data formats.

Open source vs commercial — pragmatic tradeoffs: open source lowers license fees and gives strong customization, but needs either in‑house skills or paid third‑party support for hardening, upgrades and SLA guarantees. Commercial products buy vendor support, packaged integrations and predictable onboarding at the cost of licenses and possible lock‑in. This echoes ’s point about choosing based on internal domain knowledge; it also complements ’s Drupal note — Drupal is a solid choice for content-driven intranets, while platform choice should follow the organization’s ecosystem (Office/AD shops, heavy file sync needs, etc.).

A short, practical evaluation plan: run a 4–8 week pilot with representative users and a pass/fail checklist covering SSO provisioning, document workflows, permission scenarios, search accuracy, mobile use, and a restore-from-backup exercise. Score finalists with a simple weighted matrix (example weights: usability 30, integration 25, security 20, cost 15, support/community 10) to keep decisions objective.

Operational cautions and final note: insist on clear data export and API access, a published patch/backup cadence, documented escalation paths, and at least one disaster-recovery rehearsal. For ~50 users, a managed open‑source deployment or a low‑tier SaaS commercial option often gives the best balance of cost and support while keeping future migration options open.

Recommended Answers

All 3 Replies

Member Avatar for BigPaw

Comparing the package features and associated support is a great way to start. Here are two examples:

.

Opensource.

The starkest difference between Commercial and Opensource is usually support. I could write paragraphs on the subject, but I think this site provides a very good and comprehensive explanation on the advantages and disadvantages of both options. Click here.

Member Avatar for rubberman

Have experience and domain knowledge in-house? Use open source.
Don't? Use commercial.

There is a REAL learning curve here, and having the (hopefully) hand-holding provided by a decent commercial organization can be a real help in getting started. Just remember the caveates about vendor lock-in (difficult to change down-stream when you finally think you know what you are doing), on-going support costs (N users x $N per year), etc.

Member Avatar for marie.talcod

I think Drupal is one the best solution to build an Intranet. I don't know a lot of Intranet solutions but as I work at a French Web and Open source agency (TALCOD), I do know well Drupal. Customers are quite satisfied with the Intranets we build and base on it, so it could be a great technology to suggest you.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.