Six Feet Up · Verification proof

What's verified. By what evidence. When.

The proof page lists every verification record contributing to this provider's standing. Date and level are public; client identity is anonymised unless the client opts in; underlying data sources are held in the evidence vault.

How we verify Share on X

The record, level by level.

Every level this provider has earned, with what the records at that level actually are, not a generic description. Underlying artefacts live in the evidence vault; what's disclosable is shown here.

On the spectrum · live

ReachDepth of evidenceThe moat

L0Listed
Seeded from the public record. Not yet claimed by the provider.
L1Claimed
A verified owner claims the listing and completes the structured profile.

Cross-referenced against public record.

Trustgent-attested checks of this provider's claims against independent public sources it does not control. Each item links to the source and shows when it was checked.

L2Cross-referencedCross-referenced against 2 independent sources

2026-07-02

Officially listed as a Participating Sponsor of the Python Software Foundation
python.orgConferencechecked Jul 2026
“Six Feet Up appears under the Participating Sponsors section of the PSF sponsors list.”
Named as a Gold-level sponsor at PyCon US 2018 (independent Python community conference)
us.pycon.orgConferencechecked Jul 2026
“Six Feet Up brings passion to Python web applications development and Cloud automation. We are experts in Django, Solr and Plone, and we deploy apps on a variety of private and public clouds, including AWS, Azure and Cloudflare.”

Confidentiality

Verified privately. Displayed publicly.

Trustgent verifies privately and displays publicly. The evidence vault holds the underlying artefacts, analytics screenshots, exported CSVs, dashboard read-only access tokens, audited reports. The public proof page surfaces only what the client has agreed to disclose: typically the metric, the window, and an anonymised reference to the engagement.

Every record carries its last-verified date so recency is visible on the page. Automated decay + renewal is designed but not yet live, the schedule (~24 months for L3 ratings, 18 for L4, 12 for L5) ships with the concierge intake documented on how we verify. Until then, records can be revised or retracted via the correction flow, nothing here is set-and-forget.

A cross-section of the evidence vault, records sealed behind a lockplate, a single verified thread surfacing to public view