Welcome to Nekt!
This guide walks you through the onboarding process so you can quickly set up your environment and start working with your data.Video Tutorial
For a visual walkthrough of the onboarding process, watch this video:Step 1: Create your account
- Go to
https://app.nekt.ai/signup
and enter your first name, last name, and email (preferably your company email). Click Continue. - Follow the instructions on your email to verify your account. You’ll need to define your password at this point.
- Log in with the email and password you just created.
Step 2: Create the company workspace
- Add your company logo.
- Enter your company name, size, country, and timezone. Click Continue.
Step 3: Set up your cloud environment
- Ensure you meet the following requirements:
- You have an active paid AWS account Free-tier accounts are not supported because some resources we use are only available on paid plans.
- No previous Nekt workspace exists in this AWS account. If you’ve gone through this process before, delete any related stack to avoid conflicts.
- To run your workspace with AWS, we need to create a stack. Don’t worry—we’ve pre-filled it for you. Just use the button to access and apply it.
You can understand what resources are being created on the AWS Resources Created During Setup section of this doc.
- Click Open AWS CloudFormation to be redirected to AWS with the stack ready to create.
- Keep all values as defined. We’ve configured everything you need for Nekt to run smoothly.
- Scroll down and check all checkboxes at the bottom to allow resource creation.
- Click Create stack to start the creation process.
Step 4: Set up your profile
- Add your profile picture.
- Review your name and email information. Click Continue.
- Enter your role at your company that relates to Nekt.
Step 5: Explore the Dashboard
You’ll be redirected to the Nekt Overview, where you can set up your first data source.- Click the Add Source button on the Overview page.
- Follow the guided steps to connect your first source and start bringing data into your catalog.
AWS Resources Created During Setup
The CloudFormation stack provisions the following resources in your AWS environment:Core Infrastructure
-
IAM Roles & Permissions
- ECS Service Roles: Enable source and destination connectors to access data and store it in S3
- EMR Service Roles: Allow sources and transformations to access your data catalog and perform data operations
- Frontend Access Role: Enables data preview and exploration through the Nekt application
- Server Orchestration Role: Allows Nekt to manage and coordinate all sources, destinations, and transformations
-
Lambda Functions
Custom functions that handle CloudFormation deployment tasks, including VPC IP retrieval, resource identifier notifications, and deployment completion notifications. -
Networking Infrastructure
An isolated VPC with secure network architecture:- 1 public subnet and 2 private subnets
- NAT instance with Elastic IP for secure outbound connectivity
- Internet gateway for public subnet access
- Security groups configured for each resource type
Important: Ensure your AWS region has sufficient quota for “VPCs per Region” and “Internet gateways per Region” before deployment. -
Data Storage & Catalog
- S3 Bucket: Secure storage location for all your data
- AWS Glue Databases: Managed data catalog that integrates with Nekt’s platform for metadata management
-
Container & Processing Infrastructure
- ECR Repository: Private Docker registry for custom connector and transformation images
- EMR Studio: Spark processing environment for data transformations and analysis
- ECS Cluster: Container orchestration platform for running connectors
On-Demand Resources
The following resources are provisioned automatically when you run data operations:-
AWS Fargate Tasks
Serverless container execution for source and destination connectors -
EMR Application Jobs
Spark-based processing jobs for data sources and transformations -
Amazon Athena
Interactive query service used when exploring data through Nekt’s interface
Note: The workspace setup process is automated, so you don’t need to manually configure any resources beyond running the stack.