Teedy (Sismics Docs)

Self-hosted document repository with OCR, search and access controls.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Teedy source-branch authorization and input fixes

Recent upstream source commits correct LDAP filter escaping, active-content rendering and file write-permission checks.

Scope: Reviewed main-branch fixes in October–November 2026; the older v1.11 GitHub release does not establish a release containing them.

LDAP configuration, uploaded active content and file operations have separate conditions; check the installed image’s actual commits.

Action: Verify that the installed Teedy image contains the reviewed source fixes, or obtain a fixed build; do not assume the old stable tag includes later commits.

Primary source · LDAP escaping correction · Active-content rendering correction · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Docker / Compose

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker / Compose
InfrastructureServers / containers
Teedy application, database and durable document storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The upstream feature list documents LDAP and two-factor authentication, but the reviewed installation/configuration reference does not establish a supported SAML or OIDC sign-on workflow. LDAP login alone is not evidence of federated SSO.

Self-hosted upstream edition; federation protocol and support scope unresolved · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream README includes a Docker Compose application/PostgreSQL stack and persistent volumes. It pins the example application to v1.11; reconcile it with the chosen maintained release and replace example credentials before production. Embedded H2 is evaluation-only.

Upstream Compose example, not a hardened or HA template · Source ↗ · Deployment artifact ↗ (master (moving branch; example image v1.11)) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The upstream recipe identifies the application, OCR/conversion tools, PostgreSQL and persistent storage, but does not specify a CPU/RAM minimum or validated workload sizing. Obtain a workload-specific recommendation before choosing production capacity.

Upstream production components; numeric sizing unresolved · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Teedy (Sismics Docs); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v1.11 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Teedy (Sismics Docs) upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

The published 1.11 release date and recent source activity are separate facts; do not present a source commit as a new stable release or support commitment. Verify that the installed Teedy image contains the reviewed source fixes, or obtain a fixed build; do not assume the old stable tag includes later commits.

Community & maintenance

The reviewed upstream contributor history includes jendib, naku, vmario89, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Document management
Self-hosted document repository with OCR, search and access controls.

Compare within Document management

  • Adobe Experience Manager 6.5 Forms (Correspondence Management)Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
    • AWS
    Customer-operated · Open Source / Open Core
  • Apache JSPWikiApache file-based wiki for documentation and knowledge content.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • DocassembleSelf-hosted guided interviews and automated document assembly.
    • AWS
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocspellSelf-hosted document ingestion, OCR, classification and search.
    • Railway
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
    • Azure
    Customer-operated · Commercial Only
  • eLabFTWOpen-source electronic laboratory notebook for tracked experiments, procedures and attached records.
    • Hostinger
    Customer-operated · Open Source / Open Core

Showing 8 of 41 other listings in Document management. These products address related workflows; read their category-fit notes before comparing scope. See all of Document management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger ↗ · Hostinger

      Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Teedy application, database and durable document storage. The published 1.11 release date and recent source activity are separate facts; do not present a source commit as a new stable release or support commitment.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory