diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
new file mode 100644
index 0000000..7afa760
--- /dev/null
+++ b/.github/CODEOWNERS
@@ -0,0 +1,4 @@
+# CODEOWNERS info: https://help.github.com/en/articles/about-code-owners
+# Owners are automatically requested for review for PRs that changes code
+# that they own.
+* @akon-dey @nosql22 @skrdgraph @darkn3rd
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 0000000..bee6a69
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,62 @@
+name: "🐞 Bug Report"
+description: File a bug report
+title: "[BUG]: <Title>"
+labels: ["kind/bug", "status/triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting an issue.
+        If you suspect this could be a bug, follow the template.
+  - type: textarea
+    attributes:
+      label: What version of Dgraph-Lambda are you using?
+      description: Copy and paste all you see.
+      placeholder: |
+        Paste here.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Tell us a little more about your go-environment & node-environment?
+      description: Copy and paste all you see using the command 'go version'.
+      placeholder: |
+        Paste here.
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Have you tried reproducing the issue with the latest release?
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: What is the hardware spec (RAM, CPU, OS)?
+      description: Share all possible context of your machine.
+      placeholder: |
+        Type here.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What steps will reproduce the bug?
+      description: Enter details about your bug (command/config used to run Dgraph-Lambda).
+      placeholder: |
+        Type here.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected behavior and actual result.
+      description: Enter details about your expectations.
+      placeholder: |
+        Type here.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Tell us anything else you think we should know.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..5a2fd50
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Dgraph Community Support.
+    url: https://discuss.dgraph.io/
+    about: Please ask and answer questions here.
diff --git a/.github/ISSUE_TEMPLATE/documentation_request.yml b/.github/ISSUE_TEMPLATE/documentation_request.yml
new file mode 100644
index 0000000..928c3e5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/documentation_request.yml
@@ -0,0 +1,30 @@
+name: "📃 Documentation Request"
+description: Suggest improvements, additions, or revisions to Dgraph documentation
+title: "[Documentation]: <Title>"
+labels: ["area/documentation", "status/triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting an issue.
+        If you think Dgraph's documentation at https://dgraph.io/docs/ is lacking, please explain it here.
+  - type: textarea
+    attributes:
+      label: What version of Dgraph-Lambda is the target?
+      description: Is it latest? old?
+      placeholder: |
+        Type here.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Documentation.
+      description: Explain which part of the documents is lacking.
+      placeholder: |
+          Type here.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional information.
+      description: Tell us anything else you think we should know.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 0000000..473b2f1
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,49 @@
+name: "⚡ Feature Request"
+description: Suggest a new feature
+title: "[FEATURE]: <Title>"
+labels: ["kind/feature ", "status/triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting an issue.
+        If you think we can make Dgraph better, describe your feature request here.
+        Note: Feature requests are judged based on user experience and modeled on 
+        [Go Experience Reports](https://github.com/golang/go/wiki/ExperienceReports). 
+        These reports should focus on the problems - they should not focus on and need not propose solutions.
+  - type: dropdown
+    attributes:
+      label: Have you tried Dgraph before this proposal? and did not find anything similar?
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: What you wanted to do.
+      description: Enter details about your expectations.
+      placeholder: |
+          Type here.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What you actually did.
+      description: Enter details about your experience with Dgraph-Lambda.
+      placeholder: |
+          Type here.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Why wasn't it great, with examples.
+      description: Enter details about your expectations.
+      placeholder: |
+          Type here.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional information.
+      description: Any external references to support your case.
diff --git a/.github/ISSUE_TEMPLATE/question.yml b/.github/ISSUE_TEMPLATE/question.yml
new file mode 100644
index 0000000..7becaf5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/question.yml
@@ -0,0 +1,16 @@
+name: "🙋 Question"
+description: Question related to Dgraph-Lambda
+title: "[QUESTION]: <Title>"
+labels: ["kind/question ", "status/triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        The issue tracker is not for questions.
+        - If you have a question, please try asking it on https://discuss.dgraph.io
+        - Our Docs: https://dgraph.io/docs/
+        - If it is code related, you could open it here
+  - type: textarea
+    attributes:
+      label: Question.
+      description: Ask your Question.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..64d1bf1
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,29 @@
+<!--
+ Change Github PR Title 
+
+ Your title must be in the following format: 
+ - `topic(Area): Feature`
+ - `Topic` must be one of `build|ci|docs|feat|fix|perf|refactor|chore|test`
+
+ Sample Titles:
+ - `feat(Enterprise)`: Backups can now get credentials from IAM
+ - `fix(Query)`: Skipping floats that cannot be Marshalled in JSON
+ - `perf: [Breaking]` json encoding is now 35% faster if SIMD is present
+ - `chore`: all chores/tests will be excluded from the CHANGELOG
+ -->
+
+## Problem
+ <!--
+ Please add a description with these things:
+ 1. Explain the problem by providing a good description.
+ 2. If it fixes any GitHub issues, say "Fixes #GitHubIssue".
+ 3. If it corresponds to a Jira issue, say "Fixes DGRAPH-###".
+ 4. If this is a breaking change, please prefix `[Breaking]` in the title. In the description, please put a note with exactly who these changes are breaking for.
+ -->
+
+## Solution
+ <!--
+ Please add a description with these things:
+ 1. Explain the solution to make it easier to review the PR.
+ 2. Make it easier for the reviewer by describing complex sections with comments.
+ -->
\ No newline at end of file
diff --git a/.github/workflows/ci-aqua-security-trivy-tests.yml b/.github/workflows/ci-aqua-security-trivy-tests.yml
new file mode 100644
index 0000000..a397c99
--- /dev/null
+++ b/.github/workflows/ci-aqua-security-trivy-tests.yml
@@ -0,0 +1,30 @@
+name: ci-aqua-security-trivy-tests
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+  schedule:
+    - cron: "*/30 * * * *"
+jobs:
+  build:
+    name: trivy-tests
+    runs-on: ubuntu-20.04
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+      - name: Build Docker image
+        run: |
+          make image-local
+      - name: Run Trivy vulnerability scanner
+        uses: aquasecurity/trivy-action@master
+        with:
+          image-ref: 'dgraph/dgraph:local'
+          format: 'sarif'
+          output: 'trivy-results.sarif'
+      - name: Upload Trivy scan results to GitHub Security tab
+        uses: github/codeql-action/upload-sarif@v2
+        with:
+          sarif_file: 'trivy-results.sarif'
diff --git a/.github/workflows/ci-dgraph-lambda-tests.yml b/.github/workflows/ci-dgraph-lambda-tests.yml
new file mode 100644
index 0000000..4657acc
--- /dev/null
+++ b/.github/workflows/ci-dgraph-lambda-tests.yml
@@ -0,0 +1,23 @@
+name: ci-dgraph-lambda-tests
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+  schedule:
+    - cron: "*/30 * * * *"
+jobs:
+  dgraph-tests:
+    runs-on: ubuntu-20.04
+    steps:
+      - uses: actions/checkout@v3
+      - name: Set up Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - name: Run Tests
+        run: |
+          #!/bin/bash
+          docker-compose run --rm -T -e NODE_ENV=test dgraph-lambda test
diff --git a/.gitignore b/.gitignore
index c925c21..f9726f6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,6 @@
+# IDE
+.idea
+.idea/*
+
 /dist
 /node_modules