FeedFoundry.
DEEN
Access status

Public case study

FeedFoundry in use for @gotzendorfer.at

A dated account of the rendering path, its ownership boundaries, and its visible safety limits.

As of 2026-07-11

Instagram profile @gotzendorfer.at (opens Instagram in a new tab)

Dated scope

This case study records the publicly supportable state as of 2026-07-11. It covers the Green render and publishing path.

Clear ownership

FeedFoundry is Bernhard Götzendorfer's owner-operated internal system, not a SaaS. FeedFoundry renders for @gotzendorfer.at. BuilderBob is the sole publisher there.

Permanent render-only boundary

The double-publisher incident on 2026-07-03 led to mode permanent-render-only. Recorded resolution: permanent-render-only.

2 public posts

The 2 linked Instagram posts are the primary public artifacts. Requested split; FeedFoundry used the safe hero fallback.

What the evidence shows

The artifacts show FeedFoundry in the renderer role and BuilderBob in the sole-publisher role. Visible fallback: safe.

Limits of the claim

As of 2026-07-11, the Insights status was blocked because permission instagram_manage_insights was missing. Performance conclusion: none. No reach, ROI, or engagement-lift conclusion is claimed.

Read the method