Managed Home and Open Ecosystem Compared

Where information lives, who can see it, and what each path would offer.

PimStash brings together small apps for everyday life. The managed service gives them a common home. I am also exploring AT Protocol versions for people who want to use their records through a wider ecosystem of compatible apps.

The managed service is the current product. The AT path described here is a future direction, not an available second account option.

A Managed Home

The managed service is for people who want useful tools with someone taking care of the service. Sign in to PimStash, keep your records together, and share supported collections with the people you choose.

A familiar interface across the apps means less to learn each time you use another one. Household receipts, shared recipe Books, vehicle history, and coordination with friends are natural uses.

An Open Ecosystem

The AT direction would let PimStash work with records through your AT account. The ambition is for other compatible apps to understand those records too, giving you more choice about how you use them.

The starting point is information you deliberately want to publish: a recipe, for example, or a gear list you would like others to discover. Private household records require a different promise.

What the Choice Means

Where Records Live

Managed Home

In PimStash-managed storage.

Open Ecosystem — Proposed

Through the hosting service for your AT account, which could be separate from PimStash.

Who Can See Them

Managed Home

Access is controlled by PimStash’s account and sharing rules.

Open Ecosystem — Proposed

The initial direction is deliberately public records. Private household sharing needs a separate design.

Sharing

Managed Home

Share supported collections with chosen Teams inside PimStash.

Open Ecosystem — Proposed

Make published records usable beyond PimStash where other apps support their format.

Using Other Apps

Managed Home

Supported export files let you take records out. What another app can import varies.

Open Ecosystem — Proposed

Compatible apps could use the same published records. Compatibility must be checked for each app and record type.

Who Shapes the Experience

Managed Home

One service can make coordinated choices across its apps.

Open Ecosystem — Proposed

Different apps and hosts may offer different features and experiences.

Availability

Managed Home

The current PimStash experience.

Open Ecosystem — Proposed

A future direction; AT apps are not available yet.

Can I Want Both?

Yes. You might want household receipts in a managed service and public recipes in an open ecosystem. You do not have to hold the same preference for every kind of information.

Exactly how the two paths would connect remains to be designed. Automatic synchronization and direct migration are not available promises.

Will Every App Be Available Both Ways?

That is not a commitment I am making. Each AT app needs to make sense for the information it handles and the audience that information is meant for. Recipes and private financial records have very different needs.

Does Open Mean Public?

For the initial AT direction described here, think in terms of records you intentionally publish. It would not be an alternative place to put private receipts or confidential household records. The product must make the audience clear before you publish anything.

What Happens if I Want to Leave?

The managed apps provide supported export Bundles for taking collections out. A file you can keep is useful; importing it into another product depends on that product’s support.

The AT ambition is for compatible tools to work with your records independently of the PimStash interface. I will describe the specific options as they are implemented and tested.