Getting Started

Concepts

How the product works, plus the words we use for it. Useful if you are curious about how BANANA-GOAT talks about models and sharing. You can skip this page after Quick Start if you just want to keep uploading.

The main pieces

These are the terms you will see most often in the product:

  • Source file — the raw 3D file you upload (for example .obj, .fbx, .step, .stl, .glb)
  • Secure 3D artifact — the processed result BANANA-GOAT keeps and delivers in the browser
  • Model — that processed result as it appears in your dashboard, ready to open, share, or embed
  • Share — giving someone a link to view your model
  • Embed — placing one specific model on a website for ongoing use

Source file vs what people see

The file you upload contains the important information you do not want to share. Processing turns that geometry into a secure web visualisation that is structurally different, so the important information cannot be replicated from what viewers receive.

Scraping the delivered experience is useless for recovering the original raw model. After processing, the original upload is deleted.

Model, job, share, embed

A model is the representation of your uploaded raw 3D file after it has been processed. You access it in the user dashboard.

A job is the action of processing that upload. In practice, job and model are tightly linked — one is the work, the other is the result you keep using.

A share is the act of giving a link so someone can see your model. An embed is a way to integrate one specific model on a website for a longer period of time.

Processing

Processing is the action of taking a raw 3D file — like .obj, .fbx, or .step — and turning the geometry into a secure web visualisation. That is what makes scraping useless for getting the original back.

Storage and showing

Storage is the space taken by your processed models around the clock. The models need to sit ready to show, and you pay for keeping them there.

Showing is when your model is actually shown to someone through a share or embed. That means transferring the secure artifact to their browser so they can see it. When many people view the same model, more data is transferred to more browsers — that is what showing measures.

So: storage is keeping the model ready; showing is people loading it to look at it.

Who owns what

You own your model. BANANA-GOAT stores the artifacts, but cannot see them because they are encrypted. The person with the link does not own anything — they only get permission to view while the share or embed is active.