Apps.yaml create new instances if the class is the same name

Third party integrations AppDaemon
1

Here is my app.yaml cut down for this question.

test_away_paul:
  module: "test_away_fired"
  class: "left_home"
  devicetracker_home_status: !secret device_tracker_paul
  send_alert_to: "textalertspaul"
test_home_paul:
  module: "test_home_fired"
  class: "arive_home"
  devicetracker_home_status: !secret device_tracker_paul
  send_alert_to: "textalertspaul"
test_away_nancy:
  module: "test_away_fired"
  class: "left_home"
  devicetracker_home_status: !secret device_tracker_nancy
  send_alert_to: "textalertspaul"
test_home_nancy:
  module: "test_home_fired"
  class: "arive_home"
  devicetracker_home_status: !secret device_tracker_nancy
  send_alert_to: "textalertspaul"

I am testing the sensitivity of device tracker. Once I have an understanding I will use it for other automating.
As you can see I am passing different values into class. My basic question, does all 4 in my apps.yaml get their own instance. So as long as I use “self.” variables each instance variables should have it’s own values.

I am using the code from my previous question here https://community.home-assistant.io/t/get-state-attribute-not-working/54105/10?u=penright

2 
test_away_paul:
  module: "test_away_fired"
  class: "left_home"
  devicetracker_home_status: !secret device_tracker_paul
  send_alert_to: "textalertspaul"
test_away_nancy:
  module: "test_away_fired"
  class: "left_home"
  devicetracker_home_status: !secret device_tracker_nancy
  send_alert_to: "textalertspaul"

will create 2 app instances that use the same code with different args.
so the left_home class will run twice side by side.

the same for the arrive_home class.